...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Coming Soon: Revamped Liquibase Enterprise Docs!All Liquibase Enterprise documentation will be available on docs.liquibase.com within the coming weeks! This new format will allow users to quickly find the documentation that caters directly to their user persona. All relevant content from the existing Liquibase Enterprise Documentation in Confluence Documentation and DMC Documentation sites will be migrated. |
...
Issue ID | Description |
DAT-9160 | For Postgres :: Allow custom |
DAT-8757 | For Oracle :: Fixed the forecast failure occurring with Auto-Synonym changesets in limited forecast mode. The workaround of switching to full forecast mode is no longer necessary. |
DAT-11251 | For Azure SQL Database :: Accommodate dashes in database names that caused failure during backup / restore. |
DAT-10518 | Rollback :: Fixed issue where stored logic was not being included in generated SQL when using the |
DAT-11139 | For Oracle :: Fixed issue with backup/restore on Oracle 11g databases when using |
DAT-10663 | For Oracle :: Fixed issue in forecast with sql parser enabled when using indexes on materialized views. |
DAT-10142 | For Oracle :: Fixed issue in forecast with sql parser enabled to allow reserved keyword PERIOD as a valid column name. |
Known Issues
Stored Logic State
In release 7.13 and later, we discovered that existing stored logic was in an UNKNOWN state on a Deploy report, which caused deployment to fail. We have reviewed desired behavior and will implement a storedLogicValidityAction to warn, not error, when pre-existing objects that are not part of the deployment show changes from Valid to Invalid. (DAT-9156)
...