Path: news.easynews.com!core-easynews!newsfeed3.easynews.com!easynews.com!easynews!news.glorb.com!postnews2.google.com!not-for-mail
From: shevine@aol.com (Elliott)
Newsgroups: comp.databases.oracle
Subject: Re: Locking a Table Within an INSERT
Date: 7 Jul 2004 08:35:09 -0700
Organization: http://groups.google.com
Lines: 17
Message-ID: <149413ab.0407070735.c540820@posting.google.com>
References: <149413ab.0407061210.38cc8b7d@posting.google.com> <a1d154f4.0407062334.3c557a6c@posting.google.com>
NNTP-Posting-Host: 136.1.1.154
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1089214510 2001 127.0.0.1 (7 Jul 2004 15:35:10 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 7 Jul 2004 15:35:10 +0000 (UTC)
Xref: core-easynews comp.databases.oracle:28133
X-Received-Date: Wed, 07 Jul 2004 08:34:19 MST (news.easynews.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@ford.com if you'd care to hear more.