From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-sql@postgresql.org
Subject: Re: null values in non-nullable column
Date: Tue, 19 Dec 2006 15:57:03 +0100
Message-ID: <20061219155703.21a101a4@kingfisher.sec.intern.logix-tt.com> (raw)
In-Reply-To: <8C5B026B51B6854CBE88121DBF097A8661E3FC@ehost010-33.exch010.intermedia.net>
References: <8C5B026B51B6854CBE88121DBF097A8661E3FC@ehost010-33.exch010.intermedia.net>
Hi, George,
"George Pavlov" <gpavlov@mynewplace.com> wrote:
> In 8.1 I have a situation where nullability of user defined datatypes
> does not seem to be enforced. Using the following steps I end up with a
> table that has a column that should not be nullable, but has nulls in
> it.
Ouch. That hurts!
Now all those MySQL freaks can argue "Well, PostgreSQL does allow
constraint violation, too.", despite the fact that most of them don't
even basically understand the special case we have here.
So, please, keep silent about it :-)
How difficult is it to fix this (e. G. by disallowing NULL-generating
JOINs on NOT NULL domains?)
Regards,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: schabi@logix-tt.com
Subject: Re: null values in non-nullable column
In-Reply-To: <20061219155703.21a101a4@kingfisher.sec.intern.logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox