Re: Proposal: 6NF
From: Frank Hamersley <terabitemightbe_at_bigpond.com>
Date: Wed, 11 Oct 2006 06:18:18 GMT
Message-ID: <K00Xg.45333$rP1.7287_at_news-server.bigpond.net.au>
>
> Hi Frank,
>
> No, it should not. None of the columns in the "table" is constrained to
> disallow NULLs, so the insert shoould be accepted.
>
> Sybase disallowing NULL in a column unless stated otherwise, violates
> the ANSI standards.
Date: Wed, 11 Oct 2006 06:18:18 GMT
Message-ID: <K00Xg.45333$rP1.7287_at_news-server.bigpond.net.au>
Hugo Kornelis wrote:
> On Sun, 08 Oct 2006 01:59:36 GMT, Frank Hamersley wrote:
>
> (snip)
>> Should I try it on Sybase ASE 12.5? >> >>> create table table1(field1 int, field2 varchar(1)) >>> go >>> insert table1 >>> select 1, 'A' >>> insert table1 >>> select 2, 'B' >>> insert table1 >>> select 3, 'C' >>> insert table1 >>> select NULL, 'B' >> Hmmm - the last statement fails...as it should!
>
> Hi Frank,
>
> No, it should not. None of the columns in the "table" is constrained to
> disallow NULLs, so the insert shoould be accepted.
>
> Sybase disallowing NULL in a column unless stated otherwise, violates
> the ANSI standards.
Yes I considered that and I did scratch around to see if the standard(s) were explicit on this - without much joy. There was a hint of being able to establish default settings (MS) for an implied NULL/NOT NULL clause but nothing concrete in the ANSI SQL syntax.
Do you perchance have a fast track to said explicitness?
BTW I prefer the Sybase behaviour as the alternate can only lead to sloppiness in the hands of the unwashed!
Cheers, Frank. Received on Wed Oct 11 2006 - 08:18:18 CEST