SQL Anywhere fails to create view-on-a-view if changes are performed in wrong order

[mkarg]

Search first

• I searched and no similar issues were found

Description

SQL Anywhere can define views on tables, but also views on views. At creation of the view it checks if the source table or source view does really exists. Whether this check succeeds is a race condition among the view creations: If V1 is a SELECT on V2, and V2 is created after V1, then update fails to create V1. Unfortunately, generateChangelog does not specify any particular order of the changes when reading them from a SQL Anywhere database, so V1 is tried to get created before V2 - hence update fails.

Steps To Reproduce

CREATE TABLE T (C INT);
CREATE VIEW V2 AS SELECT * FROM T;
CREATE VIEW V1 AS SELECT * FROM V2;

liquibase generateChangelog

liquibase update

Expected/Desired Behavior

Either generateChangelog produces a changelog specifying the needed sequence (V2 before V1), or update finds a way to silently resolve this situation.

Liquibase Version

master

Database Vendor & Version

SAP SQL Anywhere 17.0.11

Liquibase Integration

N/A

Liquibase Extensions

N/A

OS and/or Infrastructure Type/Provider

Windows 10 Pro (German)

Additional Context

N/A

Are you willing to submit a PR?

• I'm willing to submit a PR (Thank you!)