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?
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.
While I have always found reading the release notes an important step in architectural principles over the decades, many organizations skip over this principle and get caught off guard when there are no dedicated DBAs and architects in the engineering workforce.
Real-world examples of minor version upgrade issues
Here are two real-world situations common in the AWS RDS ecosystem using MySQL.
- You are an organization that uses RDS Aurora MySQL for its production systems, and you upgrade one minor version …