If parsing the print_transaction_message() output is tough (I find it is on long entries), you can call transaction_reader against the transaction_log to get SQL output.
As noted in the original description, there should be an entry for UPDATE'ing table c, but none will be present in the generated SQL.
from the /tests dir:
../drizzled/message/transaction_reader var/master-data/transaction.log
I've linked a branch with a test - transaction_log.bug644670, that will result in a buggy log.
./test-run --suite= transaction_ log bug64470
If parsing the print_transacti on_message( ) output is tough (I find it is on long entries), you can call transaction_reader against the transaction_log to get SQL output.
As noted in the original description, there should be an entry for UPDATE'ing table c, but none will be present in the generated SQL.
from the /tests dir: message/ transaction_ reader var/master- data/transactio n.log
../drizzled/