> ensures all your queries are posted as a single unit avoiding
> the possiblity that another transaction will not write to the
> database until this transaction completes. Always incase
> multiple transactions in a cftransaction when you are trying
> to determine a auto identity in this manor.
It's worth pointing out that this, by itself, does not guarantee that you
won't have concurrency problems. If your database allows row-level locking,
for example, the default transaction isolation level is not sufficient to
prevent problems. You will need to specify a stricter isolation level, such
as REPEATABLE_READ or SERIALIZABLE, I think.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
