Class Hibernate5ConstraintNamesPreSchemaUpgradeTask
- java.lang.Object
-
- com.atlassian.confluence.upgrade.AbstractUpgradeTask
-
- com.atlassian.confluence.upgrade.upgradetask.Hibernate5ConstraintNamesPreSchemaUpgradeTask
-
- All Implemented Interfaces:
BackupSupport
,DatabaseUpgradeTask
,UpgradeTask
,UpgradeTaskInfo
,org.springframework.beans.factory.Aware
,org.springframework.beans.factory.BeanNameAware
public class Hibernate5ConstraintNamesPreSchemaUpgradeTask extends AbstractUpgradeTask implements DatabaseUpgradeTask
Drop existing hibernate 2 constraints to allow SchemaUpdate to re-create them in the hibernate 5 naming style. Dropping the FK onstraints before the schema update (instead of after) is required for MySQL. Dropping the unique constraints before the schema update (instead of after) is required for Oracle.- Since:
- 6.1
-
-
Constructor Summary
Constructors Constructor Description Hibernate5ConstraintNamesPreSchemaUpgradeTask(HibernateDatabaseCapabilities databaseCapabilities, AlterTableExecutor alterTableExecutor, org.hibernate.SessionFactory sessionFactory)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description boolean
breaksBackwardCompatibility()
Returns true if a new export can't be imported in an older instance.void
doUpgrade()
Perform the upgrade.String
getBuildNumber()
String
getShortDescription()
A short (<50 chars) description of the upgrade actionboolean
runOnSpaceImport()
Returns true if an older Space can't be imported in a new instance without running this task.-
Methods inherited from class com.atlassian.confluence.upgrade.AbstractUpgradeTask
addAllErrors, addError, addError, getConstraint, getErrors, getName, isDatabaseUpgrade, setBeanName, setBuildNumber, validate
-
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
-
Methods inherited from interface com.atlassian.confluence.upgrade.UpgradeTask
getConstraint, getErrors, validate
-
Methods inherited from interface com.atlassian.confluence.upgrade.UpgradeTaskInfo
getName, isDatabaseUpgrade
-
-
-
-
Constructor Detail
-
Hibernate5ConstraintNamesPreSchemaUpgradeTask
public Hibernate5ConstraintNamesPreSchemaUpgradeTask(HibernateDatabaseCapabilities databaseCapabilities, AlterTableExecutor alterTableExecutor, org.hibernate.SessionFactory sessionFactory)
- Since:
- 7.20
-
-
Method Detail
-
getBuildNumber
public String getBuildNumber()
- Specified by:
getBuildNumber
in interfaceUpgradeTaskInfo
- Overrides:
getBuildNumber
in classAbstractUpgradeTask
- Returns:
- The build number that this upgrade is applicable to
-
getShortDescription
public String getShortDescription()
Description copied from interface:UpgradeTaskInfo
A short (<50 chars) description of the upgrade action- Specified by:
getShortDescription
in interfaceUpgradeTaskInfo
- Overrides:
getShortDescription
in classAbstractUpgradeTask
-
doUpgrade
public void doUpgrade() throws Exception
Description copied from interface:UpgradeTask
Perform the upgrade.- Specified by:
doUpgrade
in interfaceUpgradeTask
- Throws:
Exception
-
runOnSpaceImport
public boolean runOnSpaceImport()
Description copied from interface:BackupSupport
Returns true if an older Space can't be imported in a new instance without running this task. For example:- A task updating macro names in the BodyContent table would be blocking.
- Tasks which updates data related to the space would be blocking.
- A task upgrading the user table wouldn't be blocking.
- Adding a mandatory column on space-related content breaks space import
Note that tasks don't run on space import yet, so we just reject the import in this case.
- Specified by:
runOnSpaceImport
in interfaceBackupSupport
-
breaksBackwardCompatibility
public boolean breaksBackwardCompatibility()
Description copied from interface:BackupSupport
Returns true if a new export can't be imported in an older instance.Breaking compatibility means a snapshot of the new version will not work at all with the previous version. For example:
- A destructive operation (Some data is replaced by another) breaks backwards compatibility
- Adding a optional column does NOT break backwards compatibility
- Data is copied to another column doesn't breaks backwards compatibility
- A build number incrementation doesn't breaks backwards compatibility
- Specified by:
breaksBackwardCompatibility
in interfaceBackupSupport
-
-