<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reserved Word on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/reserved-word/</link>
    <description>Recent content in Reserved Word on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Feb 2011 17:54:40 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/reserved-word/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Interesting MySQL 5.5 upgrade gotcha</title>
      <link>https://ronaldbradford.com/blog/interesting-mysql-5-5-upgrade-gotcha-2011-02-09/</link>
      <pubDate>Wed, 09 Feb 2011 17:54:40 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/interesting-mysql-5-5-upgrade-gotcha-2011-02-09/</guid>
      <description>Today I discovered an interesting upgrade problem with a client migrating from MySQL 5.0 to 5.5. The client who is undertaking the upgrade reported that MySQL 5.5 did not support the DECIMAL(18,5) data type.</description>
    </item>
  </channel>
</rss>
