liquibase | Main Liquibase Source | Database library

This error is usually due to insufficient permissions - if the user cannot 'see' the database, liquibase silently sets it to null and then fails with this error. The best method of troubleshooting this is to connect via Snowflake web GUI with the same credentials (without setting any role or warehouse), then try running 'use database ...'. The solution is to grant enough permissions to the user - either directly or via a role (but then the role name needs to be passed on in the jdbc connection string as well).

The short version is that you are pointing to out of date XSD files in the header of your XML Changelog file. You are pointing to some marked version 2.0 - which are super old and predate the capability.

At any point, the correct ones are in the examples folder under your Liquibase installation.

For reference, as of 4.8.0, the header in the example is:

As you speak about the PROD database - of course, a better option is to make backup/restore local copy and play with it. But regarding the first part of your question you can use ssh port forwarding e.g.:

The error isn't related to your specific query, but to your dependency management.

The java.util.concurrent.Flow class has been added to the JDK 9 only, it was not yet available in the JDK 8. Starting from jOOQ 3.15, the jOOQ Open Source Edition had a Java 11 baseline and thus a direct dependency on JDK 11 API, including Flow. If you wish to continue working with Java 8 and jOOQ 3.15, you will need to upgrade to the commercial distributions, which have continued support for Java 8. You can find jOOQ's Java version support matrix here: https://www.jooq.org/download/versions

A common reason why you might still be accidentally pulling the jOOQ Open Source Edition dependency and thus run into this error, despite using the commercial editions, could be related to using a third party dependency management framework, such as Spring Boot, which defaults to depending on the jOOQ Open Source Edition. This blog post explains how to work around that: https://blog.jooq.org/how-to-use-jooqs-commercial-distributions-with-spring-boot/

Also, make sure you're using the right dependencies both in your code generation setup as well as at runtime, as you can see in this section of the manual.

It says:

This is most likely due to a bug: https://github.com/jOOQ/jOOQ/issues/12997

Behind the scenes, in jOOQ 3.16, the LiquibaseDatabase, DDLDatabase, and JPADatabase all simulate your database migrations using an in-memory H2 database. This might be changed in the future, but that's how it works now. In H2, by default, all identifiers are in upper case, and so is the configuration. This means you should be including the PUBLIC schema, not the public schema.

Note that also code generation output will contain references to PUBLIC, not public, so if you want to continue using the LiquibaseDatabase, you'll have to turn off quoting of identifiers at runtime using the RenderQuotedNames setting.

Alternatively, you don't have to use the LiquibaseDatabase, as I've mentioned elsewhere. You can also use testcontainers to run an actual migration directly on PostgreSQL, and reverse engineer an actual PostgreSQL database, instead, as described in this blog post.

By adding the PostgresDatabase in addition to the LiquibaseDatabase, you just override the LiquibaseDatabase configuration for that element. You can't specify multiple of those.

Please look at the documentation for jOOQ's LiquibaseDatabase. It mentions that the scripts property should describe a classpath location of your migration file, not a relative path location, e.g.

Your Maven configuration is useful in your development and build environments, where you depend on a live database and database connection for:

• jOOQ code generation
• Building
• Integration testing (I suspect?)

But that's different from your production database usage, where you're probably better off running Liquibase programmatically, embedded in your application. That's not the only option to run production migrations, but the one I'd recommend. Here's an official resource on the topic by Liquibase to help you make an informed decision: https://www.liquibase.com/blog/3-ways-to-run-liquibase

And here's another resource showing how to use jOOQ's code generation along with testcontainers, instead of a live database, which might help better separate build and production concerns: https://blog.jooq.org/using-testcontainers-to-generate-jooq-code/

I am having similar issues with parsing errors with husky when trying to do a git commit. I "solved" it following this answer which says that you need to add a --no-verify flag:

git commit -m "message for the commit" --no-verify

Disclaimer: this overcomes the prettier errors but does not solve it. Be sure to check that your code works properly and follows the respective code guidelines before overpassing it. After you succesfully have done that, you will not need to use the --no-verify again unless you modify that file.

The error message says, the output changeLogFile must be provided. You specified changeLogFile instead of outputChangeLogFile.