Re^2: Sequences, last_insert_id, SQLite, and Oracle

This looks like a nice technique. A couple of questions:

What's the DML for the id field?
What's the SQLite equivalent? (If there is one.)
Aren't Oracle sequences safe to use unlocked from within a transaction? I was under the impression that they do work that way, so I can request a sequence and then use it. Obviously slower than what you do above, but a little more straightforward. Hmmmm, is your id just that, a sequence?

Thanks!

Comment on Re^2: Sequences, last_insert_id, SQLite, and Oracle

Replies are listed 'Best First'.
Re^3: Sequences, last_insert_id, SQLite, and Oracle by etcshadow (Priest) on Jun 15, 2005 at 19:42 UTC
Yes, you can do this by accessing the sequence, and then inserting that value (explicitly), as two sequential statements in a transaction. What I was referring to was the standard oracle method of defining a sequence and using an on-insert trigger to bind the sequence to the id column of the table (so that inserts implicitly fetch from the sequence). For the case of the sequence used in a trigger (thus your code is not directly accessing the sequence), this is The Way. However, if you're not using triggers to pull from your sequence implicitly, then you can certainly fetch from the sequence and just use that value. `------------ :Wq Not an editor command: Wq` [download]	[reply] [d/l]

Replies are listed 'Best First'.

------------
:Wq
Not an editor command: Wq
[download]