<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mysql or Oracle Dba on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/mysql-or-oracle-dba/</link>
    <description>Recent content in Mysql or Oracle Dba on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 06 Mar 2010 19:11:09 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/mysql-or-oracle-dba/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Don&#39;t Assume – Data Integrity</title>
      <link>https://ronaldbradford.com/blog/dont-assume-data-integrity-2010-03-06/</link>
      <pubDate>Sat, 06 Mar 2010 19:11:09 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/dont-assume-data-integrity-2010-03-06/</guid>
      <description>MySQL has the same level of data integrity for numbers and strings as Oracle; when MySQL is correctly configured. By default (a reason I wish I knew why it is still the default), MySQL performs silent conversions on boundary conditions of data that will result in your data not always being what is specified.</description>
    </item>
  </channel>
</rss>
