Re: INSERT INTO foo () VALUES ()

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

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

On Tue, May 25, 2004 at 03:49:01PM +0100, Simon Cozens wrote:
> 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.

I kind of forgot the context of this question: autoincrementing primary
keys. AFAIK Oracle doesn't suppport AUTOINCREMENT per-se, but you can do
a similar thing using a trigger that pulls a value off of a sequence.
I tested the insert on a table that had such a trigger set up and it 
worked fine.

Not sure if this helps or confuses the subject more, but I thought I
should clarify.

//Ed

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