All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Comparing Transaction Isolation Levels in MySQL and MariaDB Through Automated Hermitage Testing

By

zdw

24d ago· 2 min readenInsight

Summary

This article discusses transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) in MySQL and MariaDB, comparing how they handle transaction anomalies like Read Skew and Lost Updates. The author notes that the SQL standard (including the 2023 version) remains ambiguous and allows inconsistent behavior. The article uses the concept of "Automating Hermitage" to explore differences in how MySQL and MariaDB implement transaction isolation, starting with an example of Dirty Writes.

Key quotes

· 3 pulled
Transaction isolation levels (e.g. Read Uncommitted, Read Committed, Repeatable Read, Serializable) in the official SQL standard are defined in terms of transaction anomalies like Read Skew, Lost Updates, etc.
But the SQL standard itself is ambiguous (yes, even the latest 2023 version) and allows some silly behavior.
Let's motivate this entire article by looking at the Dirty Writes.
Snippet from the RSS feed
You are getting early access to this article as a subscriber. Your support makes articles like this possible. Thank you.

You might also wanna read