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

Re: BUG #5053: domain constraints still leak

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5053: domain constraints still leak
Date: 2009-09-14 13:28:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
On Sun, Sep 13, 2009 at 10:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Andrew Gierth" <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
>> Domain NOT NULL constraints (and probably other constraints too) aren't
>> being enforced in some code paths. e.g.
> The example you give seems to tie really closely into the debate about
> whether a composite null is identically the same thing as ROW(NULL,NULL)
> or not.  In short, we have

It seems like regardless of this discussion you oughtn't to be able to
store a NULL into that table column.  But maybe I'm just confused.


In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2009-09-14 14:22:34
Subject: Re: BUG #5053: domain constraints still leak
Previous:From: Fujii MasaoDate: 2009-09-14 11:24:45
Subject: Streaming Replication patch for CommitFest 2009-09

pgsql-bugs by date

Next:From: Robert HaasDate: 2009-09-14 13:34:11
Subject: Re: BUG #5046: java developer
Previous:From: YujinDate: 2009-09-14 09:59:47
Subject: BUG #5054: PDO -> Query returns "" from Boolean type field, if it has false value.

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