about upgrading code

[ricmetal]

so my server might upgrade its mysql version at anytime.

what can i do to make sure my code wont break? where do i go to check all the changes made from version to version and is this usually a code-breaking problem?

i cant image each mysql version breaking a bunch of code of 50million websites but we gotta be sure!

[kicken]

Find out what the current version is, and the target version. Then read through the release notes and change logs which can be found in the mysql manual.

 

Most likely you won't be affected by anything, but one of the best ways to find out is to setup your site on a development server with the upgraded software and test it thoroughly. Find out what doesn't work properly and then find out why.

[ricmetal]

thanks

its good to know there might not be many code breaking changes very often.

good to hear

cheers

Edited August 11, 2013 by ricmetal

[ricmetal]

just went through the release note in a series of many MySQL versions existent between the one i currently use and the most recent ones.

i have a follow up question: does MySQL work the same on Linux and on Windows?

i ask this because i saw that i needed a different version requirement to run something, on Windows and Linux.

what a mess

Edited August 12, 2013 by ricmetal

[ricmetal]

follow up thought:

so i should always require a minimal mysql version as the latest possible to be able to install an app i create [on a server] - this way i can prevent code breaking. for instance in mysql 4.1 varchar had a limit of 255 characters. in versions after that it changed to 65k. image this being the other way around.

if i always require the latest version of mysql to be used, i can prevent any code-breaking changes when installing the app in a server with a newer mysql version.

i hope im not overthinking this but it makes sense, right?