Re: INSERT INTO foo () VALUES ()

[prev] [thread] [next] [Date index for 2004/05/25]

From: Simon Cozens
Subject: Re: INSERT INTO foo () VALUES ()
Date: 14:49 on 25 May 2004

Tony Bowden:
> On Tue, May 25, 2004 at 03:35:35PM +0100, Simon Cozens wrote:
> > > What should the SQL be in SQLite?
> > Painfully, "INSERT INTO foo VALUES (NULL)"
> 
> Is this something else that's going to differ across the various
> databases? Or is there something standard that everything will be happy
> with?

In case it helps, inserting NULL into an auto-incrementing PK does the
right thing on mysql as well as SQLite. It doesn't work on Postgres.

        -- 
        People who love sausages, respect the law, and work with IT standards
shouldn't watch any of them being made.
    - Peter Gutmann

INSERT INTO foo () VALUES ()
Simon Cozens 13:55 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
Tony Bowden 14:13 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
Simon Cozens 14:35 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
Tony Bowden 14:37 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
ed-cdbi 14:42 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
Simon Cozens 14:49 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
ed-cdbi 15:13 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
cees-cdbi 15:47 on 25 May 2004

Re: INSERT INTO foo () VALUES ()
Branislav Zahradnik 16:20 on 25 May 2004

RE: INSERT INTO foo () VALUES ()
"g 06:00 on 26 May 2004

Re: INSERT INTO foo () VALUES ()
Edward J. Sabol 14:40 on 26 May 2004