Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null
Date
Msg-id 2675.1281637611@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null  ("Mariusz Majer" <mmajer@janmedia.com>)
Responses Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null  ("mmajer@janmedia.com" <mmajer@janmedia.com>)
List pgsql-bugs
"Mariusz Majer" <mmajer@janmedia.com> writes:
> There has been a table ecom2_orders for a while (~0.5m records). After
> executing query:

> ALTER TABLE ecom2_orders ADD COLUMN password_pdf character varying(50);

> when new rows are added, column password_pdf is filled with 'UL' value
> rather than null

Works fine here.  Perhaps you have an incorrect build of 8.3.11?

Another possibility is that you omitted some important step.
Ordinarily, \d wouldn't show any explicit "default" modifier for a
column created as above.  Maybe you did an ALTER SET DEFAULT in a
strange way?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5611: SQL Function STABLE promoting to VOLATILE
Next
From: Robert Haas
Date:
Subject: Re: BUG #5613: cannot delete