DAT-4118

SQL Parser: a nested create index statement in the unique constraint for create table breaks the parser.

DAT-4581

SQL Parser unable to forecast the unique index and primary key when scripted within the CREATE TABLE command. In release 7.12, we fixed the following:

• The issue with the generation of the create index change related to a primary key constraint:

  • The column tag generated incorrectly for multiple columns

• The issue with the generation of the create index change related to unique constraints:

  • The column tag generated incorrectly for multiple columns

  • The tableName attribute missed for the generated create index change

DAT-5171

SQL Parser: duplicate index forecast errors if script drops an index and then creates an index. SQL Parser does not model the drop of the index, which results in duplicate index error. 

DAT-5943

SQL Parser: the forecast fails when packaging a CREATE MATERIALIZED VIEW script that contains the clause USING INDEX TABLESPACE.

DAT-6779

SQL Parser adds an incorrect SELECT statement with scripts that are altering partitions.

DAT-7013

SQL Parser: parentheses and semicolon symbols ); in a create table ddl script lead to the creation of a tag changeset.

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.