> > I actually wasn't saying it shouldn't have a unique constraint, just > that if you're using cflock to handle the looping and checking, then the > system will never actually reach a point at which the unique index > becomes relevant, because the lock will prevent it from even attempting > to insert any dup's.
I wasn't saying you weren't - just pointing out that it should ;) What I am saying though is that the check and the insert can be the same thing - why use two uniqueness checkers when one is already written for you and is water tight? Loop until the db doesn't throw back a unique constraint error when you try and insert. Seems to me the most logical approach (and it doesn't require a lock). Dominic -- Blog it up: http://fusion.dominicwatson.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:298828 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
