Bugfix - when using transactions (InnoDB), ALL insert sets must get correctly committed

or rolled back. insertLastReceivedId was not committed, and as we reuse the cursor, reader
client kept getting stale data until next event insert on the same connection, possibly
from completely different client at completely unrelated time (which unintentionally
closed even the previous transaction), or until server restart. Whew, tricky beast to hunt.