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?
no, you haven't ... The correlations were implemented internally in JIRA
I am willing to accept the answer if
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.