Comments - System-Versioned Tables

5 years, 10 months ago Sergei Golubchik

Unfortunately, no. The only reason for mysql.transaction_registry to exist is because transaction end cannot be stored directly in the versioned table. (simply, because it's not known at the time of the operation, it is only known at the time of commit, and it wold be too costly to postpone all updates till the commit time)

You can create a view that joins with mysql.transaction_registry so for your users the join will be hidden and implicit.

If it's a question of privileges, you can just grant everyone SELECT privilege on mysql.transaction_registry, and they can join, when needed.

 
5 years, 10 months ago Al Bunch

Not the answer I wanted, but it does make perfect sense. The next best thing would be to somehow put the transaction_registry table directly in the database with the versioned tables themselves so it's at least self-contained.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.