<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Integrity on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/data-integrity/</link>
    <description>Recent content in Data Integrity on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Jun 2024 20:29:00 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/data-integrity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The curse of MySQL warnings</title>
      <link>https://ronaldbradford.com/blog/the-curse-of-mysql-warnings-2024-06-10/</link>
      <pubDate>Mon, 10 Jun 2024 20:29:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/the-curse-of-mysql-warnings-2024-06-10/</guid>
      <description>MySQL warnings are an anti-pattern when it comes to maintaining data integrity. When the information retrieved from a database does not match what was entered, and this is not identified immediately, this can be permanently lost.</description>
    </item>
    <item>
      <title>Why SQL_MODE is essential even when not perfect</title>
      <link>https://ronaldbradford.com/blog/why-sql_mode-is-essential-even-when-not-perfect-2012-02-16/</link>
      <pubDate>Thu, 16 Feb 2012 19:00:51 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/why-sql_mode-is-essential-even-when-not-perfect-2012-02-16/</guid>
      <description>In a recent rant on Why I think SQL_MODE is useless… , I wanted to counteract this statement with why we MUST all use SQL_MODE, even with the inherit flaws.</description>
    </item>
    <item>
      <title>MySQL Idiosyncrasies That Bite</title>
      <link>https://ronaldbradford.com/blog/mysql-idiosyncrasies-that-bite-2010-06-28/</link>
      <pubDate>Mon, 28 Jun 2010 17:38:49 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/mysql-idiosyncrasies-that-bite-2010-06-28/</guid>
      <description>The following are my slides that I presented at ODTUG Kaleidoscope 2010 . This presentation talks about the MySQL defaults including a non-transactional state, silent data truncations, date management, and transaction isolation options.</description>
    </item>
  </channel>
</rss>
