Rob Sciuk <[EMAIL PROTECTED]> wrote: > On Wed, 30 Aug 2006, Mario Frasca wrote: > > On 2006-0829 13:15:02, [EMAIL PROTECTED] wrote: > > > > >> To my surprise (perhaps "horror") I find that SQLite has > > >> for a very long time allowed NULL values in PRIMARY KEY > > >> columns. [...] > > > > I understand your concern about legacy programs, but most of us expect > > PRIMARY KEY to imply NOT NULL... don't we? what about looking for > > alternative good solutions? we could put the correction code in the > > source, conditionally compiled (not the default) and with the next major > > release reverse the condition (new 'corrected' source becomes default > > and old 'legacy' behaviour still available if desired) ... ? > > > > I have to go along with Mario, here. This is a potential show stopper,
Show stopper? Really? The bug has been there for years, literally, and nobody has even noticed it until now - despite thousands of users and millions and millions of deployments. There is a really simple work-around: Just add NOT NULL to your PRIMARY KEY column declaration... -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
