Closed jozefmorvay closed 7 months ago
I am getting the same error. It is like the catalogs object is coming as null when I am using it with the MySQL database
Any help?
I am getting the same error. It is like the catalogs object is coming as null when I am using it with the MySQL database
Any help?
@muasif Did you ever figure this out? Running into the exact same issue.
Hello,
Adding this line to my gradle dependencies worked for me :
liquibaseRuntime 'org.springframework.boot:spring-boot-starter-data-jpa'
But it seems like you already got it.
Should be a problem with another dependency.
I´m running into the same issue, but I don´t use Spring JPA but Quarkus with Panache instead
Hello, Did anyone ever find a solution to this? Running into the same issue..
I had this Problem: I defined the ref URL in the liquibase.properties file. And put a Multiline string there.
referenceUrl:"hibernate:spring:de.cop.business.model\
?dialect=org.hibernate.dialect.SQLServerDialect"
I forgot that Properties is not yaml and "
is invalid.
Removing the "
worked. Parsing the URI should really be validated before executing on it.
I´m running into the same issue, but I don´t use Spring JPA but Quarkus with Panache instead
Hello, I was able to resolve this today. just include spring-data-jpa and spring-data-envers in liquibaseRuntime. That should solve the issue. I am afraid I ran into multiple issue when configuring with quarkus . I believe we should have equivalent support with Quarkus just like spring bean with reference url like hibernate:quarks:<entitiespackage>?dialect=<hibernateGenericDialect>
something like this
Hi - we have some fixes and workarounds on this answer. Please reopen the issue if it is not fixable by using any of them.
Hello. I am unable to get this running for my project on java 11 with spring boot. My build.gradle:
When running either diff or diffChangeLog, I am getting this:
This is caused by HibernateConnectionMetadata class, which I do not understand the purpose of. It just returns null/0/false for everything. So then I tried commenting out
referenceDriver 'liquibase.ext.hibernate.database.connection.HibernateDriver'
and replaced the line with:driver 'org.postgresql.Driver'
But that amounted to getting a new exception instead:No idea what that means since postgre driver is clearly listed as a liquibaseRuntime dependency. This may not be an issue of this project, I am rather looking for an advice how to proceed.
┆Issue is synchronized with this Jira Bug by Unito