Comments - SET TRANSACTION

3 weeks, 5 days ago Alexander Peresypkin

For REPEATABLE READ, the documentation states: "For a unique index with a unique search condition, InnoDB locks only the index record found, not the gap before it." However, after the bug https://jira.mariadb.org/browse/MDEV-30225 was fixed with the commit https://github.com/MariaDB/server/commit/3ddc00dc3bf29f7cf326268265e47fda61e6a83e, a next-key lock is set for a unique secondary index even with a unique search condition. Should the documentation be updated accordingly?

 
3 weeks, 4 days ago Ian Gilfillan

Thanks, this has been updated.

 
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.