Re: Null vs. Empty String in Postgres 8.3.8 - Mailing list pgsql-general

From Tim Landscheidt
Subject Re: Null vs. Empty String in Postgres 8.3.8
Date
Msg-id m3sk79yldr.fsf@passepartout.tim-landscheidt.de
Whole thread Raw
In response to Null vs. Empty String in Postgres 8.3.8  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
List pgsql-general
Peter Hunsberger <peter.hunsberger@gmail.com> wrote:

>>> I still don't get it.  I do want a zero for the subversion_flags to be stored in the table.  But it returned an
errorbecause it didn't like subversion_flags='' in the UPDATE SQL statement. 

>>> subversion_flags | integer       | not null default 0

>> Right. '' is not 0.  the old version of pgsql converted '' to 0 for
>> you, incorrectly.  Now if you want 0 you need to say 0.

> Or, since you have the default, set it to null.... (Which may be what
> you thought you where doing?)

Setting it to NULL does not set it to the default value. You
have to use the keyword DEFAULT for that.

Tim

pgsql-general by date:

Previous
From: "Andrus"
Date:
Subject: Re: How to fix set-valued function called in context that cannot accept a set in earlier versions
Next
From: Gerhard Heift
Date:
Subject: Temporal data storage