[MariaDB] Error on generatechangelog due to sequence error

Environment

Liquibase Version: 3.8.9

Liquibase Integration & Version: CLI

Liquibase Extension(s) & Version: none

Database Vendor & Version: MariaDB Skysql

Operating System Type & Version: N/A

Description

C:\dev\skysql>liquibase generatechangelog
Liquibase Community 3.8.9 by Datical
Unexpected error running Liquibase: liquibase.exception.UnexpectedLiquibaseException: Don't know how to query for sequences on <username> @ jdbc:mariadb://<domain>:<port>/mysql?useSSL=true&serverSslCert=/<path>/skysql_chain.pem (Default Schema: mysql)
For more information, please use the --logLevel flag

Steps To Reproduce

1. Create account at https://cloud.mariadb.com/skysql
2. Create a Skysql database.
3. Get the connection information and run snapshot or generatechangelog.

Actual Behavior

See above.

Expected/Desired Behavior

Generates a changelog.

Additional Context

note the two params at the end of the url: useSSL and serverSslCert. You’ll need those to connect…

Workaround

This error can be avoided by excluding any sequences when running any diff commands, for example:

liquibase --diffTypes=catalog,tables,functions,views,columns,indexes,foreignkeys,primarykeys,uniqueconstraints,storedprocedure,triggers --changeLogFile=newChangeLog.xml generateChangeLog

QA Manual Test Requirements

Setup

• Follow the steps in the description to setup and connect to a SkySQL database OR use MariaDB 10.4.12 locally.

  • Load the MariaDB sample database: https://www.mariadbtutorial.com/getting-started/mariadb-sample-database/

• Create a sequence on the database

• Execute a Liquibase snapshot without using --diffTypes

• Execute a Liquibase generateChangeLog without using --diffTypes

• Execute a Liquibase diffChangeLog without using --diffTypes For all test cases, ASSERT ::

• Liquibase operation is successful

• The sequence is included in the output file (snapshot or changelog).

QA Automation Requirements

• None

┆Issue is synchronized with this Jira Bug by Unito ┆fixVersions: Liquibase 3.10.2

[sync-by-unito[bot]]

➤ Nathan Voxland commented:

The fix for this is in # 1176 LB-287

[robstoll]

Bug also occurs with MariaDB 10.5.3