-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
3.5
-
3.05
-
While installing the WAR version of JIRA 3.5 I had forgotten to fix the entityEngine.xml to mssql. When I logged in to JIRA it said that the database type mapping was incorrect and to change it, which I did and then restarted JIRA.
JIRA then crashed fairly spectacularly with a SQLException while executing the following:INSERT INTO propertyentry (ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype) VALUES (?, ?, ?, ?, ?) (Cannot insert the value NULL into column 'ID', table 'jac_production_db.jirauser.propertyentry'; column does not allow nulls. INSERT fails. For full details/pain please see https://support.atlassian.com/browse/JSP-3966
So, if JIRA can tell that the database mapping is incorrect, shouldn't it NOT create the tables incorrectly? It would have saved me quite a bit of pain. Also, if it can tell, why do we need to set it explicitly in the first place?
- is related to
-
JRASERVER-5947 JIRA 3.1 fails to upgrade JIRA 3.0.x data using jTDS driver (SQL Server and Sybase)
-
- Closed
-
- relates to
-
JRASERVER-599 Create Installer for JIRA standalone
- Closed