...
Issue ID | Description | |||
DAT-9160 DAT- DAT- | Fixed the issue that prevented psql change types from handling custom arguments. Psql change types can pass custom arguments successfullyFor Postgres :: Allow custom | |||
DAT-88848757 | Fixed the out of memory issue that occurred when packager ran with too large SQL files. | Fixed the SqlServer eror that occurred when statements existed prior to CREATE OR ALTER PROCEDURE. | DAT-8757 | Fixed the forecast failure that occurred when Limited Forecast did not include autoSynonymForObjects changeset schemas in profilesFor 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 | Fixed the For Azure SQL Database packaging issue that caused packaging to fail:: Accommodate dashes in database names that caused failure during backup / restore. | |||
DAT-10520 | Fixed the | DAT-10518 | Fixed the storedlogic rollback issue that did not provide a generated SQL when | Rollback :: Fixed issue where stored logic was not being included in generated SQL when using the |
DAT-11139 | Fixed the Oracle DATAPUMP issue so the optimization backup and restore method for packaging successfully works For Oracle :: Fixed issue with backup/restore on Oracle 11g databases when using |
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)
Limited Forecast does not include autoSynonymForObjects changeset schemas in profiling
In release 7.13 and later, if you use Limited Forecast in Oracle multi-schema projects with auto synonyms, you might get errors about the schema targeted by an auto synonym change being for a schema that cannot be managed, even though that schema is included in the project definition. If you encounter such errors with version 7.18, use Full Forecast instead of Limited Forecast. (DAT-8757)
Missing SSH Preferences in Liquibase Enterprise & Business GUI
After upgrading Datical DB to later versions, you might have issues with the SSH feature being unavailable to generate the SSH key via the Eclipse GUI. To return SSH in Preferences, follow these steps:
In the Datical DB GUI, select Help > Install New Software.
In the Work with field of the Install dialog box, paste in this link: https://download.eclipse.org/releases/2018-12 then hit enter.
Expand open the Collaboration category.
Enable the checkbox to select Git integration for Eclipse, and then select Next to install it.
When it finishes installing, you will be prompted to restart.
Open File > Preferences > General > Network Connections. You should now have a new SSH2 option under Network Connections.
Liquibase Enterprise & Business cannot pick up SQLPATH environment variable on Windows
In release 7.6 and later, we updated the version of instantclient, which provides SQLPLUS 12.2.0.1.0. This version of SQLPLUS contains a bug: SQL PLUS 12.2 NOT OBSERVING SQLPATH IN REGISTRY OR ENV VARIABLE FOR LOGIN.SQL. As a workaround, use SQLPLUS 12.1 on Windows. (DAT-7598)
Documentation for v8.0
Documentation for the base release is available in the following forms:
...