Details
-
Bug
-
Resolution: Fixed
-
Medium
-
2.6.1 Pro
-
PostgreSQL 7.3 and up
-
2.06
-
Description
PostgreSQL 7.3 an up support schemas. Ofbiz' Entity Engie whcih is used for database communication in JIRA does not handle that very well. During startup the following will appear in the log files:
2004-04-01 14:20:18,428 WARN [core.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database
2004-04-01 14:20:18,517 ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "jiraaction"
2004-04-01 14:20:18,517 ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE jiraaction (ID NUMERIC(18,0) NOT NULL, issueid NUMERIC(18,0), AUTHOR VARCHAR(255), actiontype VARCHAR(255), actionlevel VARCHAR(255), actionbody TEXT, CREATED TIMESTAMP, actionnum NUMERIC(18,0), CONSTRAINT PK_jiraaction PRIMARY KEY (ID))
Error was: java.sql.SQLException: ERROR: Relation 'jiraaction' already exists
for every table in the database.
JIRA will continue to work.
The problem is more serious when upgarding from a previous version of JIRA, as in version 2.6 extra columns were created (since 2.5). During startup ofbiz fails to determine that the table exists and tries to create it, as the table is actually there the creation fails. Ofbiz does not try to add extra columns after that. When JIRA tries to export data before running the upgrade tasks the export fails as some columns do not exist in the database.