Quick question:
I read in this posting here: http://archives.neohapsis.com/archives/dev/sapdb/2003-q2/0459.html
that the difference between db_offline and db_stop was that db_offline broke transactions first, whereas db_stop was like "pulling the plug."
However, I did some tests and found that in fact, both commands abort my transactions, just the same. Is there really a difference between these two commands?
Also:
So if there's no way to wait for transactions to finish, is it best to do some form of (ugly, I know):
LOCK (WAIT) TABLE <all tables used in potential sessions> in EXCLUSIVE MODE
And then when I have the locks, shut down the database?
This method would, of course, assume that the programmer of whatever application doesn't use multiple transactions for a business process (because, is it any better to have all of a customer's credit card information, but not their order??), and has AUTOCOMMIT set to off.
Thanks for your input. JLS
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
