Rob Sciuk wrote:
On Wed, 30 Aug 2006, Mario Frasca wrote:
I understand your concern about legacy programs, but most of us expect
PRIMARY KEY to imply NOT NULL... don't we?
<MHO>
I have to go along with Mario, here. This is a potential show stopper,
I would not be that negative, but at least to me it is a small
nuisance... in a piece of software I have, I need some testing scripts
for the 4 supported dbms. with sqlite primary key not implying not
null, I'm not sure what is the best way to go. adding explicit NOT NULL
after primary key for all engines goes against my sense for aestetics.
not a show stopper for sqlite, but maybe in contrast with the front page
line:
«Implements most of SQL92.»
and I would grab a "fixed" version of SQLite ASAP were it made available.
Alternatively, one might simply use an ifdef to restore the old (legacy)
behaviour, something like:
#ifdef WEIRD_AND_UNEXPECTED_BEHAVIOURS_DESIRED
funny name for a symbol... I had to laugh about it, but I'm afraid that
it is not quite too self explicative... we all have read Borges'
Library, haven't we? (There are also letters on the spine of each book;
these letters do not indicate or prefigure what the pages will say)
greetings,
Mario
p.s.:
I see that some other 'anonymous' has added an #ifdef request to ticket
518...
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
