David Karr wrote:
it's supposedly good advice in a multi-step stored procedure to have an
explicit "start transaction" and "commit" wrapping the work. What is the
impact of doing this if the stored procedure is called from code managed by
a transaction manager. For instance, in a JEE appserver and a transaction
manager?
Impact should be NONE.
If AUTOCOMMIT is already OFF then the BEGIN TRANSACION should have 0 effect,
now as to the "COMMIT" - you need to darn sure what the STATE of things
are vis-avis
your TRANSACTION Manger, as i could possibly be setting AUTOCOMMIT off
and the "COMMIT: wil turn it ON!
I think you are , at some point, likely to chop your wang off mixing 2
different Transaction control mechanisms.
For example - Which one handles ROLLBACKS
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
