there is no need at all to lock anything. Once you get the nextval from the sequence, it is yours to keep. Another thread, request, user what have you will get a differnt value guarnteed. You will have to use two queries to return the value though, but again, no locking is needed. DK
On 5/12/05, Aaron Rouse <[EMAIL PROTECTED]> wrote: > > It is SEQNAME.NEXTVAL in Oracle and I'd like to see how you get that to > work > in a single CFQUERY that returns NEWID to the CFM page. Using two > CFQUERies > would at least avoid the need to "lock" anything. > > On 5/12/05, Douglas Knudsen <[EMAIL PROTECTED]> wrote: > > > > with oracle vernacular the word is sequence. Just perform a query to > > return > > the next value in the sequence, then use it in your inserts. > > SELECT seqname.next_val as newid FROM dual > > INSERT INTO tablefoo (id, goo) VALUES (newid, 'soem stuff') > > DK > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:11:2623 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/11 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:11 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.11 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
