Guillaume Smet a écrit :
On 1/31/07, Gérard BUNEL <[EMAIL PROTECTED]> wrote:That's OK, my recoveryLog is also a mysql database. If it's a problem for you and if the recovery log is not too long, youI've used mysqldump and the following record is the last inserted in the recovery table, and corresponds to what is in the database (398) after enabling it. But it's not what's in the other database nor in the other controller recoveryLog. INSERT INTO `RECOVERY` (`log_id`, `vlogin`, `sql_data`, `sql_data_param`, `auto_conn_tran`, `transaction_id`, `request_id`, `exec_status`, `exec_time`, `update_count`) VALUES("1196", "TEST", "update Counter set COUNTER=? where ID=?", "<!%L|398|!%><!%S|Singleton|!%>", "T", "183", "366", "S", "2", "1"); INSERT INTO `RECOVERY` (`log_id`, `vlogin`, `sql_data`, `sql_data_param`, `auto_conn_tran`, `transaction_id`, `request_id`, `exec_status`, `exec_time`, `update_count`) VALUES("1195", "TEST", "begin", NULL, "T", "183", "0", "S", "0", "-1"); INSERT INTO `RECOVERY` (`log_id`, `vlogin`, `sql_data`, `sql_data_param`, `auto_conn_tran`, `transaction_id`, `request_id`, `exec_status`, `exec_time`, `update_count`) VALUES("1194", "TEST", "commit", NULL, "T", "182", "0", "S", "0", "0");
--
Gérard
BUNEL |
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia

