<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nextbaseline on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/nextbaseline/</link>
    <description>Recent content in Nextbaseline 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, 19 Jun 2024 15:54:01 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/nextbaseline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Database testing for all version changes  (including minor versions)</title>
      <link>https://ronaldbradford.com/blog/database-testing-for-all-version-changes-including-minor-versions-2024-06-19/</link>
      <pubDate>Wed, 19 Jun 2024 15:54:01 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/database-testing-for-all-version-changes-including-minor-versions-2024-06-19/</guid>
      <description>We know that SQL statement compatibility can change with major database version upgrades and that you should adequately test for them. But what about minor version upgrades?&#xA;It is dangerous to assume that your existing SQL statements work with a minor update, especially when using an augmented version of an open-source database such as a cloud provider that may not be as transparent about all changes.</description>
    </item>
  </channel>
</rss>
