From: "Spencer" Newsgroups: comp.databases.oracle.server References: <57fq9tkfvmsqnsja55sd70o6blbq2dt33d@4ax.com> <97l2qo$mbm$1@s1.read.news.oleane.net> <3A9E4470.1C8F8114@chello.nl> Subject: Re: Re: Sequence Number Re-use is it possible, what is the standard Lines: 49 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: <7yfo6.385$na.7150@nnrp1.sbc.net> Date: Sat, 3 Mar 2001 17:58:54 -0600 NNTP-Posting-Host: 208.190.213.153 X-Complaints-To: abuse@swbell.net X-Trace: nnrp1.sbc.net 983663875 208.190.213.153 (Sat, 03 Mar 2001 17:57:55 CST) NNTP-Posting-Date: Sat, 03 Mar 2001 17:57:55 CST Organization: SBC Internet Services have you considered postponing the assignment of the unique sequence number until a row is actually inserted into the table? i'm thinking that your "problem" could be resolved with a small change to the application design. a "bid" isn't really a "bid" until it is "saved", so it doesn't really make sense to acquire and assign a unique key until it is inserted into the table. sequences are designed to solve the need for a unique identifier. just a thought. wrote in message news:r.983458782.1579010009@[208.50.67.66]... > Thanks for the response. > > We are already using NOCache. I think we are just wondering if anyone has put > the unused numbers into another table so the front-end can get it from there or > the sequence number to not have big gaps. > > I also added functionality on the front-end to show a screen to ask them to > save, if they haven't already, so it won't skip as much. I know that will help > tremendously. > > However, when we get to some of our more complex systems, like our purcahsing > system, it might need a more elegant solution. > > Thank you everyone who has replied so far. > > Mark > > > > > > > > > -- > Spam protected message from: > Sent by mspritzler from sasco within field com > Posted via http://www.usenet-replayer.com/cgi/content/new