We have recently converted a JIRA 4.1 Installation from using MyISAM to using InnoDB. When doing the same for Confluence, foreign key constraints have to be added. However, it seems that a fresh installation of JIRA 4.1 does not create any foreign key constraints at all.
When upgrading to 6.0, only a few constraints are created for Active Objects, but none for "internal" JIRA Tables.
The information on the web is very slim, only a pdf by a third party can be found easyily, which claims that "the JIRA database does not enforce foreign keys and does not actually use the same data type for foreign keys in all cases".
Is that correct? Do I need to create no foreign key constraints after switching from MyISAM to InnoDB?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs