as long as the lock has a name specified, yes.... it's exclusive. Hwever, do you have (or will you ever create) any code that updates the-one-you're-inserting-in anywhere else that may not be in the same named lock? I believe cftrans would prevent this kind of conflict, where this locking would not. Do you see what I mean?

__________/ Ian Westbrook \__________
> That way you'll have them both at the same time, and wont have to worry
> about anyone inserting anything else at the same time.

but the same with lock, surely? type=exclusive means other requests are
queued until the action within the lock completes, no?

or at least that's what I thought...

Ian W


--
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]



Reply via email to