<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>REPEATABLE-READ on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/repeatable-read/</link>
    <description>Recent content in REPEATABLE-READ on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Sep 2009 06:33:04 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/repeatable-read/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Innodb Transaction Isolation</title>
      <link>https://ronaldbradford.com/blog/understanding-mysql-innodb-transaction-isolation-2009-09-24/</link>
      <pubDate>Thu, 24 Sep 2009 06:33:04 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/understanding-mysql-innodb-transaction-isolation-2009-09-24/</guid>
      <description>The MySQL Innodb storage engine provides ACID compliance, the ‘I’ being isolation. There are four states defined in MySQL with the tx_isolation system variable, READ-UNCOMMITTED, READ-COMMITTED, REPEATABLE-READ and SERIALIZABLE.&#xA;Generally MySQL installations do not modify the default value of tx_isolation = REPEATABLE-READ, however I have seen with a number of clients the default value has been changed to READ-COMMITTED.</description>
    </item>
  </channel>
</rss>
