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

Re: BUG #1582: boolean DEFAULT TRUE results in FALSE for NULL values

From: Eric McGough <emcgough(at)yahoo(dot)com>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1582: boolean DEFAULT TRUE results in FALSE for NULL values
Date: 2005-04-11 16:50:11
Message-ID: 20050411165011.64398.qmail@web31508.mail.mud.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-bugs
I made a mistake.

Postgres does put a NULL in the field (albiet I would still like to see
postgres/COPY change the NULL to TRUE if DEFAULT is set to true), it
appears pgAdmin III version 1.2.0 is the one displaying a boolean NULL
as FALSE (as opposed to NULL).

Sorry for not testing a little bit more before posting.

Thanks to all of you who responded.




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

pgsql-bugs by date

Next:From: Bruno Wolff IIIDate: 2005-04-11 17:18:28
Subject: Re: BUG #1581: Problem with capitalised DB names...
Previous:From: Tom LaneDate: 2005-04-11 16:46:17
Subject: Re: BUG #1592: "with hold" cursor problem

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