JIRA 4.0 : JIRA 4.0 Database Schema Changes for MySQL and Oracle
This page last changed on Oct 05, 2009 by rosie@atlassian.com.
If you are using the MySQL or Oracle database, two column data types have been changed as described in the JIRA 4.0 Database Schema Changes section below. Recommended method of upgradeThe easiest way to upgrade to JIRA 4.0 is to perform an XML backup and restore as described in the Upgrading JIRA instructions. Alternative method of upgradeIf in the past, instead of performing an XML backup and restore, you have been upgrading by "pointing" the new version of JIRA at an old database, this is still possible. However, the procedure is more complicated. You will need to use SQL scripts to perform database schema changes. MySQL notes for alternative method of upgrade
Note: The following warnings regarding database changes can be ignored. They will only appear the first time you start JIRA after upgrading your JIRA database to 4.0. main WARN [core.entity.jdbc.DatabaseUtil] Entity "ExternalGadget" has no table in the database main WARN [core.entity.jdbc.DatabaseUtil] Entity "GadgetUserPreference" has no table in the database main WARN [core.entity.jdbc.DatabaseUtil] Entity "Issue" has 24 fields but table "jiraissue" has 23 columns. main WARN [core.entity.jdbc.DatabaseUtil] Field "resolutiondate" of entity "Issue" is missing its corresponding column "RESOLUTIONDATE" main WARN [core.entity.jdbc.DatabaseUtil] Entity "PortletConfiguration" has 7 fields but table "portletconfiguration" has 6 columns. main WARN [core.entity.jdbc.DatabaseUtil] Field "gadgetXml" of entity "PortletConfiguration" is missing its corresponding column "GADGET_XML" Oracle notes for alternative method of upgrade
Note: The following warnings regarding database changes can be ignored. They will only appear the first time you start JIRA after upgrading your JIRA database to 4.0. main WARN [core.entity.jdbc.DatabaseUtil] Entity "ExternalGadget" has no table in the database main WARN [core.entity.jdbc.DatabaseUtil] Entity "GadgetUserPreference" has no table in the database main WARN [core.entity.jdbc.DatabaseUtil] Entity "Issue" has 24 fields but table "jiraissue" has 23 columns. main WARN [core.entity.jdbc.DatabaseUtil] Field "resolutiondate" of entity "Issue" is missing its corresponding column "RESOLUTIONDATE" main WARN [core.entity.jdbc.DatabaseUtil] Entity "PortletConfiguration" has 7 fields but table "portletconfiguration" has 6 columns. main WARN [core.entity.jdbc.DatabaseUtil] Field "gadgetXml" of entity "PortletConfiguration" is missing its corresponding column "GADGET_XML" JIRA 4.0 Database Schema ChangesThe table below summarises the changes to the database schema. Please note that if you have developed any custom utilities which query or modify the JIRA database directly (i.e. without using the JIRA API), you need to check whether the utilities need to be updated. Column data typesThe following database column data types have been changed. Their column name, old and new data types, as well as the database table they belong to, are shown below: For MySQL:
For Oracle:
|
![]() |
Document generated by Confluence on Oct 06, 2009 00:26 |