Skip site navigation (1) Skip section navigation (2)

Re: Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "mmajer(at)janmedia(dot)com" <mmajer(at)janmedia(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null
Date: 2010-08-13 19:01:54
Message-ID: 5295.1281726114@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"mmajer(at)janmedia(dot)com" <mmajer(at)janmedia(dot)com> writes:
> 1. SQL queries where executed using JDBC.
> 2. I was trying to repeat the bug (executing 'direct queries', from psql)- I
> created a new table, added some rows, then alter table adding varchar column
> field (password_pdf) with DEFAULT NULL, added some rows problem does not
> occur neither in 8.3.11 nor 8.1.19 - so it is not easy to repeat it 

Maybe JDBC is an essential aspect somehow?  Although if it had messed up
the ALTER TABLE command you'd think that would be visible in the \d output.

It would be useful to see the stored version of the default in the
misbehaving table, ie

	select * from pg_attrdef where adrelid = 'ecom2_orders'::regclass;

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: william.a.deanDate: 2010-08-13 19:26:49
Subject: DROP CONSTRAINT IF EXISTS
Previous:From: Tom LaneDate: 2010-08-13 18:53:46
Subject: Re: BUG #5619: restore won't work with files transferred with NFS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group