Re: Locking a Table Within an INSERT

From: Elliott <shevine_at_aol.com>
Date: 7 Jul 2004 08:35:09 -0700
Message-ID: <149413ab.0407070735.c540820_at_posting.google.com>

> Use a sequence
> replace the horrible expression by
> <sequence>.nextval and you are set.
>
> Sybrand Bakker
> Senior Oracle DBA

Would that I could. Unfortunately, the business requirements are that I know the generated values in advance of inserting them.

I've thought of establishing an intermediate table into which I could insert the values from a sequence, together with other record identifying information, to be used in a lookup later. But I'm dealing with, in some cases, a couple of million rows per run, with a dozen runs a day.

You can write me at eshevin_at_ford.com if you'd care to hear more. Received on Wed Jul 07 2004 - 17:35:09 CEST

This message: [ Message body ]
Next message: D Rolfe: "Re: Locking a Table Within an INSERT"
Previous message: Mark D Powell: "Re: Get calling instance information in external procedure"
Maybe in reply to: Elliott: "Locking a Table Within an INSERT"
In reply to sybrandb_at_yahoo.com: "Re: Locking a Table Within an INSERT"
Next in thread: D Rolfe: "Re: Locking a Table Within an INSERT"
Reply: D Rolfe: "Re: Locking a Table Within an INSERT"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message