Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In release 7.12, we improved the Oracle SQL Parser usability, which allows you to benefit from forecast capabilities for Oracle SQL scripts packaged through the DIRECT package method. The main fixes include constraints and indexes. See the following table with the issues addressed for more details.

...

Issue ID

Description

DAT-5850

Alignment and line ending deviation between the sql_direct and procedure folders. Procedures packaged through the sql_direct folder have alignment issues. From now on, the script can be formatted and aligned similarly regardless of the packaging folder.

DAT-6529

A false forecast rule failure when more than one script is packaged.

DAT-6766

Packager missed scripts that were merged and reverted in git. The packager logic has been enhanced to check for all the needed files.

DAT-6813

Liquibase Enterprise support for Db2 LUW 11.5.

DAT-6827

The stored logic versioning does not work as expected as it cannot be reverted by copying an older version from the SCM. When Packager runs, it cannot package a new version of the updated script. From now on, you can check a copy of the previous version of the code and get a new versioned changeset created for it.

DAT-6922

GUI: Unable to run operations after enabling and then disabling runtime credentials.

DAT-7062

The issue with calculating checksum for sqlFile after the DaticalDB upgrade. In release 7.11, we discovered that a changelog which contains sqlFile Change Types causes checksum validation errors. The issue is fixed in release 7.12.

DAT-7222

Azure MI: connection retry logic is broken due to updates in Azure PITR (point in time restore). The issue is fixed in release 7.12. When using Azure MI, you need to grant the appropriate permissions: GRANT VIEW SERVER STATE TO [#{dbusername}]. SeeĀ Roles and Permissions for Datical DB and Azure SQL Managed Instance.

Deployment Monitoring Console (DMC) Issues

...