We recently updated from mysql 5.0 to 5.6 (took a mysqldump and restored on a new server) we then received a timestamp error so we added the parameter zeroDateTimeBehavior=convertToNull' to our jdbc connection string, now it appears that dates get updated with 0000-00-00 instead of the correct date
I believe that jumping from 5.0 to 5.6 is a huge step. I would recommend going to 5.5 and then 5.6 after testing each upgrade and confirming that everything is working fine. The mySQL documentation should help too.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG