I wrote:
> I propose that we define typdefault as containing the *external*
> representation of the desired value, and have get_typdefault apply the
> type's input conversion function to produce a Datum. Any objections?
This change is committed for 7.2.
regards, tom lane
>> Uh, what did your CREATE TYPE command look like, exactly? This sounds
>> like you specified a default value for the datatype.
> [ no, he didn't ]
Now that I look at it, CREATE TYPE is totally whacked out about default
values for user-defined datatypes. The reason the system-defined types
al
Dave Blasby <[EMAIL PROTECTED]> writes:
> CREATE TABLE test_table (myint integer, mydata MY_DATATYPE);
> INSERT INTO test_table VALUES (1);
> At this point, I'd expect there to be one row in test table. The myint
> column will have the value one, and the mydata column will have the
> value NULL.
It took me a while to figure out what was going on, but I think I've
figured it out.
Lets say you have your own variable length datatype called
'MY_DATATYPE'.
CREATE TABLE test_table (myint integer, mydata MY_DATATYPE);
INSERT INTO test_table VALUES (1);
At this point, I'd expect there to be on
