TLDR
-
Open-source tool Monastery automates Hermitage-style transaction anomaly tests across MySQL and MariaDB at multiple isolation levels.
Key Takeaways
-
The SQL standard’s isolation level definitions are ambiguous even in the 2023 version, leaving room for inconsistent database behavior.
-
Dirty Writes are prevented by all major databases despite the spec allowing them; Dirty Reads are permitted at Read Uncommitted level.
-
Monastery adapts Lorin Hochstein’s bowling shoe thought experiment into executable multi-database test scripts.
-
MySQL and MariaDB diverge in transaction behavior despite shared lineage; Monastery surfaces those differences concretely.
-
PostgreSQL omits Read Uncommitted entirely, sidestepping Dirty Read exposure.
Hacker News Comment Review
-
No substantive HN discussion yet.
Original | Discuss on HN
