It would defeat the entire purpose of a transactions to allow a lock to be released during a transaction.
Specifically, as the purpose is keep all related updates within the same transaction. If this next key update function does not need or *should* not to be rolled back, then this shouldn't be part of the transaction at all. I'm guessing a rollback of this key would cause serious implications. :-) As Stuart suggests...a redesign of update process to make the transaction smaller maybe your only course of action. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boydell, Stuart Sent: Thursday, May 10, 2007 11:11 AM To: u2-users@listserver.u2ug.org Cc: [EMAIL PROTECTED] Subject: RE: [U2] Locks in a transaction Make sure that you do as little processing as possible within the actual transaction so that the transaction is short and sweet. Other than that, there is absolutely no way a lock should be released before a transaction completes. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
