Re: Wrong column default values - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: Wrong column default values
Date
Msg-id 6489.1253398696@sss.pgh.pa.us
Whole thread Raw
In response to Re: Wrong column default values  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Kris Jurka <books@ejurka.com> writes:
>> On Fri, 18 Sep 2009, Tom Lane wrote:
>>> Indeed.  In 8.3 it seems that even if you try to set the default that
>>> way, the system will throw away the cast:

>> That's only true without a typmod.

> Hmm, maybe that could use improvement.

I looked at this a bit and found that AddRelationNewConstraints
will throw away a plain null Const default, but what it's actually
seeing in these cases is an invocation of the type's length coercion
function on a null Const.  We could possibly add more code to throw
that away too (probably conditionally on the length coercion function
being strict, else it might have processing to do for a null).  It
doesn't really seem worth it though.  I think the OP's problem is
most elegantly solved by not writing "default null" in the first place.
It's certainly the only solution that he's likely to see payback from
in less than a year's time ...

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: Wrong column default values
Next
From: Hannu Krosing
Date:
Subject: Re: OOM on large SELECT