From: | Denver Timothy <denver(at)timothy(dot)io> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Unexpected custom type behavior using ROW(NULL) |
Date: | 2015-03-15 00:21:27 |
Message-ID: | A7639483-F6EC-4D5E-8A60-6D3D653B7E79@timothy.io |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In 9.4.1, I do this:
CREATE TYPE my_test_type as (part1 text, part2 text);
\pset null NULL
WITH test_table(test_col) AS (
VALUES (NULL::my_test_type), (ROW(NULL, NULL)::my_test_type)
)
SELECT *, (test_col).part1, (test_col).part2, test_col IS NULL AS is_null FROM test_table;
And I get this result:
┌──────────┬───────┬───────┬─────────┐
│ test_col │ part1 │ part2 │ is_null │
├──────────┼───────┼───────┼─────────┤
│ NULL │ NULL │ NULL │ t │
│ (,) │ NULL │ NULL │ t │
└──────────┴───────┴───────┴─────────┘
But I expect this result:
┌──────────┬───────┬───────┬─────────┐
│ test_col │ part1 │ part2 │ is_null │
├──────────┼───────┼───────┼─────────┤
│ NULL │ NULL │ NULL │ t │
│ NULL │ NULL │ NULL │ t │
└──────────┴───────┴───────┴─────────┘
Is this expected behavior? I do find references in the docs to input/output of NULL values as components of anonymous record types, but it's still not clear to me if this would be expected behavior after a cast to a custom type.
Is there a trick to get the result I'm expecting? So far all of the syntactical gymnastics I can think of still produce the same result.
I'm a long time PostgreSQL user, but custom types is fairly new to me, so any insight or pointers to appropriate reading would be helpful.
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Dusek | 2015-03-15 02:09:44 | Re: regclass and format('%I') |
Previous Message | Tom Lane | 2015-03-14 19:28:30 | Re: is there a relationship between indexes and temporary file creation? |