Barney Boisvert wrote: > That's a horrible way to do it. Quite inefficient. > > A better route is to check your DB's docs and see how they expose the > last inserted sequence value. In MySQL it's LAST_INSERT_ID(), with MS > SQL Server its one of three @IDENTITY variables. Run your INSERT, and > then select the value back out using this mechanism. You may or may > not need a transaction, depending on the specifics, and you definitely > won't need CFLOCK.
That's only reliable inside a transaction. Don't leave that part out. - Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:4:192385 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
