Open rharding6373 opened 12 months ago
Should be fixed by the type-coercion fix.
Confirmed that we no longer have an internal error, however our error and error code differs from postgres:
CRDB:
ERROR: could not parse "42" as type tuple{int AS x, varchar AS y}: record must be enclosed in ( and )
SQLSTATE: 22P02
postgres:
ERROR: 42804: cannot return non-composite value from function returning composite type
I think that postgres's Data Type Mismatch is much more helpful than Invalid Text Representation. But since they both error I think this is a low priority and probably easy fix.
Repro:
Stacktrace:
postgres returns the following error:
Found in pg_regress plpgsql
Jira issue: CRDB-33718