> As long as the DBMS enforces the transaction suggested by ColdFusion > your approach should be fine and as others have suggested, > auto-incrementing the particular field might be better left to other > mechanisms at the DBMS level. > > However, providing you are happy to handle it in ColdFusion, your > example code is unnecessarily complicated. Doing the following will > achieve precisely the same effect:
JUST AS LONG as you have a primary key! I have found this not to work with MS-SQL-2000 when the id col (by accident) had it's pk index missing. zac **************************************************************************** This email and any files transmitted with it is confidential and are intended solely for the use of the individual or entity to whom they are addressed. Any confidentiality is not waived or lost because this email has been sent to you by mistake. This email may contain personal information of individuals, and be subject to Commonwealth and/or State privacy laws in Australia. This email is also subject to copyright. If you are not the intended recipient, you must not read, print, store, copy, forward or use this email for any purpose, in accordance with privacy and copyright laws. If you have received this email in error, please notify the sender by return email, and delete this email from your mailbox. **************************************************************************** ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
