Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
Description
NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.
HibernateAlterTableExecutor uses the exception message to detect if an exception, such as "the constraint you're adding already exists", can be ignored.
It doesn't work on non-english database with the following databases: MySql, Postgres, Sql Server & HSQLDB.
Resulting to this kind of exceptions:
[atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized Upgrade failed, application will not start: Upgrade task com.atlassian.confluence.upgrade.upgradetask.ContentPermissionConstraintsUpgradeTask@6f4ea4a2 failed during the SCHEMA_UPGRADE phase due to: StatementCallback; bad SQL grammar [alter table CONTENT_PERM alter column CPS_ID set not null, add constraint cp_unique_user unique (CPS_ID, CP_TYPE, USERNAME), add constraint cp_unique_group unique (CPS_ID, CP_TYPE, GROUPNAME)]; nested exception is org.postgresql.util.PSQLException: FEHLER: Relation »cp_unique_user« existiert bereits
2011-09-21 12:40:36,530 WARN [main] [confluence.upgrade.upgradetask.AbstractConstraintCreationUpgradeTask] doUpgrade Could not create unique constraint: alter table cwd_user add constraint cwd_user_name_dir_id unique (lower_user_name, directory_id), StatementCallback; bad SQL grammar [alter table cwd_user add constraint cwd_user_name_dir_id unique (lower_user_name, directory_id)]; nested exception is org.postgresql.util.PSQLException: FEHLER: Relation »cwd_user_name_dir_id« existiert bereits
Attachments
Issue Links
- is related to
-
-
- Closed
-