You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
we upgraded from an older liquibase version to 4.3.2 and introduced this HANA extension. In the past we had own implementations for HANA-specific data types and operations which we removed. We are using a central db changelog (XML) which consists only of includes of other changelog files.
In the beginning of the central changelog we have a central properties XML to specify data types for different databases, e.g.
So we are using the attribute dbms to specify database-specific data types and in the other changelogs for specifying database-specific operations.
The attribute dbms="hdb" is not recognized and the property substitutions are not working anymore, as well as other db operations using this attribute value. If we remove it, then it works.
What is the correct attribute to be used within the dbms attribute for HANA using this liquibase extension for HANA?
Hello,
we upgraded from an older liquibase version to 4.3.2 and introduced this HANA extension. In the past we had own implementations for HANA-specific data types and operations which we removed. We are using a central db changelog (XML) which consists only of includes of other changelog files.
In the beginning of the central changelog we have a central properties XML to specify data types for different databases, e.g.
So we are using the attribute dbms to specify database-specific data types and in the other changelogs for specifying database-specific operations.
The attribute dbms="hdb" is not recognized and the property substitutions are not working anymore, as well as other db operations using this attribute value. If we remove it, then it works.
What is the correct attribute to be used within the dbms attribute for HANA using this liquibase extension for HANA?
Thanks and best regards,
P1ll3P4ll3
┆Issue is synchronized with this Jira Bug by Unito
The text was updated successfully, but these errors were encountered: