JIRA 3.7 Database Schema Changes
Due to the upgrade of HSQLDB, and to improve compatibility with Firebird and Frontbase, various database tables and columns have been renamed.
The 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), please check whether the utilities need to be updated.
Tables
The following database table has been renamed:
OLD TABLE NAME |
NEW TABLE NAME |
|---|---|
version |
projectversion |
Columns
The following database columns have been renamed. Their old and new names, as well as the database table they belong to are shown below:
TABLE NAME |
OLD COLUMN NAME |
NEW COLUMN NAME |
|---|---|---|
notification |
type |
notif_type |
notification |
parameter |
notif_parameter |
mailserver |
type |
server_type |
jiraeventtype |
type |
event_type |
schemepermissions |
type |
perm_type |
schemepermissions |
parameter |
perm_parameter |
fieldlayout |
type |
layout_type |
schemeissuesecurities |
type |
sec_type |
schemeissuesecurities |
parameter |
sec_parameter |
portletconfiguration |
position |
positionseq |
Special note for MS SQL Server
Additionally to the schema changes described above, for MS SQL Server, all columns of type TEXT have been changed to NTEXT to ensure that international characters can be safely stored.