updated database from mysql 5.0 to 5.6

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

2 answers

0 vote

Hi Matthew, 


Did you try a re-index after you add the jdbc paramenter?


Renato Rudnicki 

Hi Matthew,

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.




Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,323 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot