this is happening for any callers of drizzled::write_bin_log the transaction GPB message gets constructed before a transaction is actually started in inno. Not sure what a good solution is for this, while we could just add in TransactionServices::rawStatement() a call to start a transaction in inno this would allocate a id that can then be used that doesnt seem like the correct solution
this is happening for any callers of drizzled: :write_ bin_log the transaction GPB message gets constructed before a transaction is actually started in inno. Not sure what a good solution is for this, while we could just add in TransactionServ ices::rawStatem ent() a call to start a transaction in inno this would allocate a id that can then be used that doesnt seem like the correct solution