From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: null values in non-nullable column |
Date: | 2006-12-19 14:57:03 |
Message-ID: | 20061219155703.21a101a4@kingfisher.sec.intern.logix-tt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi, George,
"George Pavlov" <gpavlov(at)mynewplace(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios | 2006-12-19 15:05:01 | Re: Query a select that returns.... |
Previous Message | Markus Schaber | 2006-12-19 14:23:00 | Re: Autovaccum |