tursopg: parse the text in a cast to uuid - #11600

• Minor Description says ENCODE reads every PostgreSQL spelling; '{a0eebc999c0b4ef8bb6d6bb9bd380a11}'::uuid fails with invalid UUID value, PostgreSQL accepts it
  Suggested fix: Say that braces without hyphens and hyphens after any 4-digit group are rejected, and urn:uuid: text is accepted, unlike PostgreSQL

main gets these wrong too, so this change did not cause them.

1. Casting a valid UUID with a hyphen after any 4 digits, or braces with no hyphens, to uuid fails

Every text cast to uuid (and every insert into a uuid column) that PostgreSQL accepts but the uuid crate's Uuid::parse_str rejects fails with 'invalid UUID value': braces around 32 plain hex digits, and hyphens after any group of 4 hex digits other than the standard 8-4-4-4-12 places. The reverse case also fails: 'urn:uuid:<uuid>' is accepted, but PostgreSQL rejects it.

Input:

SELECT '{a0eebc999c0b4ef8bb6d6bb9bd380a11}'::uuid;
SELECT 'a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11'::uuid;
SELECT 'urn:uuid:a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'::uuid;

This PR:

ERROR: invalid UUID value / ERROR: invalid UUID value / a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11

main:

{a0eebc999c0b4ef8bb6d6bb9bd380a11} / a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11 / urn:uuid:a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11 (text returned unchanged)

PostgreSQL:

a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11 / a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11 / ERROR: invalid input syntax for type uuid: "urn:uuid:a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"

2. An invalid text cast to uuid fails with SQLSTATE P0001 instead of 22P02

Every text cast to uuid that does not parse fails with SQLSTATE P0001 (raise_exception) and the message 'invalid UUID value'. PostgreSQL gives 22P02 and 'invalid input syntax for type uuid: "..."'. Inserting bad text into a uuid column gives the same wrong SQLSTATE.

Input:

\set VERBOSITY verbose
SELECT 'bogus'::uuid;

3. Casting bytea, integer, numeric or boolean to uuid is accepted or gives the wrong error

Every cast to uuid from a type other than text or uuid (bytea, integer, numeric, boolean) should fail with 'cannot cast type X to uuid' (SQLSTATE 42846). Instead, bytea of exactly 16 bytes becomes a uuid, and the other types fail with 'invalid UUID value'.

Input:

SELECT '0123456789abcdef'::bytea::uuid;
SELECT 123::uuid;

• tursopg uuid input rejects some spellings PostgreSQL accepts and accepts urn:uuid: text: CREATE TABLE t(u uuid); INSERT INTO t VALUES ('{a0eebc999c0b4ef8bb6d6bb9bd380a11}'); INSERT INTO t VALUES ('a0ee-bc99-9c0b4ef8-bb6d-6bb9bd380a11'); INSERT INTO t VALUES ('urn:uuid:a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'); SELECT u FROM t;
• tursopg: comparing a uuid or date column with a differently written string literal finds no rows: CREATE TABLE d(x date, u uuid); INSERT INTO d VALUES ('2024-01-05', 'a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'); SELECT count(*) FROM d WHERE x = '2024-1-5'; SELECT count(*) FROM d WHERE u = 'A0EEBC99-9C0B-4EF8-BB6D-6BB9BD380A11';
• Casting a uuid to bytea or integer is accepted instead of failing: SELECT 'a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11'::uuid::int; SELECT 'A0EEBC99-9C0B-4EF8-BB6D-6BB9BD380A11'::uuid::bytea;

1. Refuted: postgres/parser/translator.rs:6527: Column path may differ: inserting uppercase or braced text into a uuid column may not normalize it
   → INSERT of uppercase and braced text into a uuid column reads back lowercase with hyphens on main and on this pull request, as in PostgreSQL timeout 60 $b -q :memory: < /tmp/q2.sql
2. Refuted: postgres/parser/translator.rs:6527: The bare name "uuid" must match the core built-in type name
   → Same literal is used by the column mapping (translator.rs:6096) and for date/time in the same match; core registers CREATE TYPE uuid; new sqltests fail if the name is wrong timeout 1500 make -C postgres/conformance run-one FILE=pg-sqltests/select.sqltest
3. Refuted: postgres/conformance/pg-sqltests/select.sqltest:333: New tests may not pass on real PostgreSQL
   → All three uuid tests pass against PostgreSQL 18; the one failure in the file is an unrelated LIKE test timeout 900 cargo run -q --manifest-path ../../testing/sqltest/Cargo.toml --bin sqltest -- run pg-sqltests/select.sqltest --backend postgres --postgres-dsn "$PG_DSN"
4. Refuted: postgres/parser/translator.rs:6527: json_to_record also uses this mapping; behavior change there
   → json_to_record(...) AS x(a uuid) now returns lowercase like PostgreSQL; main returned the uppercase text timeout 60 $b -q :memory: < /tmp/q2.sql