Tagged with "innodb"

2019-03-04 23:15 UTC

Fun MySQL fact of the day: `REPEATABLE READ` isn't `REPEATABLE WRITE`

Since we're on the topic of transaction isolation, you might have previously had a mental model that transaction isolation levels are a layered model, each one stronger than the next. Unfortunately, this isn't quite true; and if that's not annoying enough, you might even be surprised to learn that ... read more

2019-03-01 21:18 UTC

Fun MySQL fact of the day: InnoDB read-only optimisation

The I in ACID stands for Isolation, which is a property that determines whether or not a transaction can see the progress of other transactions. Transaction isolation is a complex system generally defined by the allowance of certain "read phenomena". ... read more

2019-02-28 21:36 UTC

Fun MySQL fact of the day: chaos without `ORDER BY`

ANSI SQL-92 states that the order of a result set in the absence of an ORDER BY is implementation specific. This means that the same query without an ORDER BY clause run n times may return rows in n different orders. ... read more

2019-02-27 21:55 UTC

Fun MySQL fact of the day: no nested transactions

Nested transactions allow a client to begin and end multiple transactions within an outer transaction (within an outer transaction (within an outer transaction (within an outer transaction ...))). When would you use it? This type of mechanism is necessary to accomplish a pure Component Based Architecture. However, excepting BerkleyDB, nearly ... read more

« Previous 1 2 3 4

Tagged with "innodb"

Fun MySQL fact of the day: REPEATABLE READ isn't REPEATABLE WRITE

Fun MySQL fact of the day: InnoDB read-only optimisation

Fun MySQL fact of the day: chaos without ORDER BY

Fun MySQL fact of the day: no nested transactions

Fun MySQL fact of the day: `REPEATABLE READ` isn't `REPEATABLE WRITE`

Fun MySQL fact of the day: chaos without `ORDER BY`