Ask Tom describes this well with regards to Oracle: http://www.oracle.com/technology/oramag/oracle/05-nov/o65asktom.html
The drawback (with Oracle at least) is that if one tries to update the same row from two different serializable transactions, you'll get an error. Of course this can be trapped and appropriate action taken. On Feb 13, 2008 12:28 AM, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > s. isaac dealey wrote: > >> The transaction won't actually isolate you from a race condition. > >> Other connections will be able to insert at the same time. A full > >> table lock, on the other hand, will protect you. A unique key > >> constraint would also do it. > > > > Umm... I was under the impression that a serializable transaction lock > > would lock the table. > > It doesn't: > http://jochem.vandieten.net/2008/02/12/serializable-transactions-are-not-single-threading-a-database/ > > > > this is from the CF7 docs for cftransaction: > > > > * serializable: places an exclusive lock on every data table in use for > > the duration of the transaction. Causes access to the database to be > > single-threaded and is therefore not recommended for normal database > > access. > > http://livedocs.adobe.com/coldfusion/7/htmldocs/00000346.htm > > That is a documentation bug that has been fixed in CF 8. > > Jochem > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:298841 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
