Hibernate ORM SchemaManagementException when running tests #25607

leonardowestphal · 2022-05-16T15:13:03Z

When updating an application from Quarkus 2.1.4 to version 2.4.0, it started to show a schema validation error when starting the application with the command: mvn quarkus:dev.

Failed to start application (with profile dev): org.hibernate.tool.schema.spi.SchemaManagementException: SQL strings added more than once for: '<table_name>'
        at org.hibernate.tool.schema.internal.SchemaCreatorImpl.checkExportIdentifier(SchemaCreatorImpl.java:409)
        at org.hibernate.tool.schema.internal.SchemaCreatorImpl.createFromMetadata(SchemaCreatorImpl.java:314)
        at org.hibernate.tool.schema.internal.SchemaCreatorImpl.performCreation(SchemaCreatorImpl.java:167)
        at org.hibernate.tool.schema.internal.SchemaCreatorImpl.doCreation(SchemaCreatorImpl.java:136)
        at org.hibernate.tool.schema.internal.SchemaCreatorImpl.doCreation(SchemaCreatorImpl.java:122)
        at org.hibernate.tool.hbm2ddl.SchemaExport.doExecution(SchemaExport.java:314)
        at io.quarkus.hibernate.orm.runtime.devconsole.HibernateOrmDevConsoleInfoSupplier.generateDDL(HibernateOrmDevConsoleInfoSupplier.java:77)
        at io.quarkus.hibernate.orm.runtime.devconsole.HibernateOrmDevConsoleInfoSupplier.pushPersistenceUnit(HibernateOrmDevConsoleInfoSupplier.java:35)

I noticed that this error also occurs in versions prior to 2.4.0 and that in version 2.4.1 or higher this error was corrected, however, when running the tests, a similar error occurs: mvn test...
I have the same error with: mvn clean package...

java.lang.RuntimeException: java.lang.RuntimeException: Failed to start quarkus
Caused by: java.lang.RuntimeException: Failed to start quarkus
Caused by: java.lang.RuntimeException: javax.persistence.PersistenceException: [PersistenceUnit: Pu1] Unable to build Hibernate SessionFactory
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: Pu1] Unable to build Hibernate SessionFactory
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: SQL strings added more than once for: <table_name>

I also noticed post-boot validation errors:

(Hibernate post-boot validation thread for App1) Failed to validate Schema: Schema-validation: wrong column type encountered in column...

As it is a legacy system and I cannot change the hibernate mappings or the database, I ended up using the following properties to resolve post-boot errors:

quarkus.hibernate-orm."Pu1".database.generation=none
quarkus.hibernate-orm."Pu1".validate-in-dev-mode=false
quarkus.hibernate-orm."Pu2".database.generation=none
quarkus.hibernate-orm."Pu2".validate-in-dev-mode=false

There are two Persistence Units that use the same mappings!
I'm using java 11, Maven 3.8.1, and currently on Quarkus 2.9.0.

@Sanne @yrodiere @gsmet
Any ideas to solve the schema validation problem when running the tests? I tried to create a new project and reproduce the problem, but I couldn't.

The text was updated successfully, but these errors were encountered:

quarkus-bot · 2022-05-16T15:13:06Z

/cc @Sanne, @gsmet, @yrodiere

leonardowestphal · 2022-05-16T18:31:58Z

I think I just found the solution.
I believe that some behavior of the test execution profiles has been changed.
Using version 2.1.4, as I was running only locally, I had only set the property: '%dev.quarkus.datasource...'
But with the updated version I also need a property without the 'dev' profile: 'quarkus.datasource...'

The error presented in the log didn't help me much. I think it would be nice to evaluate to see if there is any improvement in the Hibernate ORM extension or another point to make the reason clearer.

luisnuxx · 2022-05-22T18:35:54Z

i'm also facing this issue after upgrading an existing app ( SQL Server ) from Quarkus 1.9.2.Final to 2.9.1.Final ( Flyway extension is being used as well )

yrodiere · 2022-06-01T14:13:46Z

Sorry, but I'm not sure I understand what the problem is here...

From what I've read:

In 2.4.0, you started seeing an exception with HibernateOrmDevConsoleInfoSupplier.generateDDL in the stacktrace, but that was fixed in 2.4.1.
You're seing a "similar" error for mvn test/mvn clean package, but that's expected since (from what you're saying) your schema cannot pass validation, and this is fixed by setting database.generation=none/validate-in-dev-mode=false (without the %dev prefix).
You want to be able to prefix the configuration property with %dev, and have this automatically applied to tests... ? That's not what the dev profile is about. There's also a test profile (%test), maybe that's what you're after?

Can you show me a full configuration that you expect to work, the full command line that you're using to build/start/test the application, and the full stack trace that you're getting (please don't remove any line starting with Caused by/at)?

yrodiere · 2022-06-09T13:37:03Z

Can you show me a full configuration that you expect to work, the full command line that you're using to build/start/test the application, and the full stack trace that you're getting (please don't remove any line starting with Caused by/at)?

Note that even if you can't provide a full reproducer, the information above might be enough to at least understand what the problem is :)

leonardowestphal · 2022-06-09T19:38:31Z

Sorry, but I'm not sure I understand what the problem is here...

From what I've read:

In 2.4.0, you started seeing an exception with HibernateOrmDevConsoleInfoSupplier.generateDDL in the stacktrace, but that was fixed in 2.4.1.

You're seing a "similar" error for mvn test/mvn clean package, but that's expected since (from what you're saying) your schema cannot pass validation, and this is fixed by setting database.generation=none/validate-in-dev-mode=false (without the %dev prefix).

You want to be able to prefix the configuration property with %dev, and have this automatically applied to tests... ? That's not what the dev profile is about. There's also a test profile (%test), maybe that's what you're after?

Can you show me a full configuration that you expect to work, the full command line that you're using to build/start/test the application, and the full stack trace that you're getting (please don't remove any line starting with Caused by/at)?

Hi @yrodiere

I solved the problem by adding the "quarkus.datasource" property.

The main fact is that until version 2.1.4 the tests worked even without the "quarkus.datasource" property (there was only this property with %dev profile) and the stack trace is not showing the real reason, making it difficult to find or understand what is going on.

My application.properties without %prod properties, without the fix and without sensitive data:

quarkus.http.port=8080
%dev.quarkus.http.port=8083

quarkus.datasource."DB1".db-kind=postgresql
quarkus.datasource."DB1".username=user
quarkus.datasource."DB1".password=password
%dev.quarkus.datasource."DB1".jdbc.url=jdbc:postgresql://<ip>:5432/<db_name>

quarkus.hibernate-orm."DB1".datasource=DB1
quarkus.hibernate-orm."DB1".database.default-schema=schemaDB1
quarkus.hibernate-orm."DB1".discriminator.ignore-explicit-for-joined=true
quarkus.hibernate-orm."DB1".fetch.max-depth=1
quarkus.hibernate-orm."DB1".packages=<package_name>
quarkus.hibernate-orm."DB1".database.generation=none
quarkus.hibernate-orm."DB1".validate-in-dev-mode=false

quarkus.datasource."DB2".db-kind=postgresql
quarkus.datasource."DB2".username=user
quarkus.datasource."DB2".password=password
%dev.quarkus.datasource."DB2".jdbc.url=jdbc:postgresql://<ip>:5432/<db_name>

quarkus.hibernate-orm."DB2".datasource=DB2
quarkus.hibernate-orm."DB2".database.default-schema=schemaDB2
quarkus.hibernate-orm."DB2".discriminator.ignore-explicit-for-joined=true
quarkus.hibernate-orm."DB2".fetch.max-depth=1
quarkus.hibernate-orm."DB2".packages=<package_name>
quarkus.hibernate-orm."DB2".database.generation=none
quarkus.hibernate-orm."DB2".validate-in-dev-mode=false

# Jandex for Hibernate Entities
quarkus.index-dependency.<name>.group-id=<group-id>
quarkus.index-dependency.<name>.artifact-id=<artifact-id>
quarkus.index-dependency.<name>.classifier=classes

# Cache
quarkus.hibernate-orm."DB1".cache."<cache_name1>".expiration.max-idle=300
quarkus.hibernate-orm."DB1".cache."<cache_name1>".memory.object-count=25000
quarkus.hibernate-orm."DB2".cache."<cache_name1>".expiration.max-idle=300
quarkus.hibernate-orm."DB2".cache."<cache_name1>".memory.object-count=25000

quarkus.hibernate-orm."DB1".cache."<cache_name2>".expiration.max-idle=600
quarkus.hibernate-orm."DB1".cache."<cache_name2>".memory.object-count=2000
quarkus.hibernate-orm."DB2".cache."<cache_name2>".expiration.max-idle=600
quarkus.hibernate-orm."DB2".cache."<cache_name2>".memory.object-count=200

...more cache...

Command:
mvn clean test

Test execution error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project <project_name>: There are test failures.
[ERROR] 
[ERROR] Please refer to <project_path>/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project <project_name>: There are test failures.

Please refer to <project_path>/target/surefire-reports for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures.

Please refer to <project_path>/target/surefire-reports for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
    at org.apache.maven.plugin.surefire.SurefireHelper.throwException (SurefireHelper.java:271)
    at org.apache.maven.plugin.surefire.SurefireHelper.reportExecution (SurefireHelper.java:159)
    at org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary (SurefirePlugin.java:453)
    at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked (AbstractSurefireMojo.java:1175)
    at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute (AbstractSurefireMojo.java:932)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Error stack trace:

[ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 54.489 s <<< FAILURE! - in <package>.<test_class>
[ERROR] <package>.<test_class>.<method_name>  Time elapsed: 0.036 s  <<< ERROR!
java.lang.RuntimeException: java.lang.RuntimeException: Failed to start quarkus
Caused by: java.lang.RuntimeException: Failed to start quarkus
Caused by: java.lang.RuntimeException: javax.persistence.PersistenceException: [PersistenceUnit: DB1] Unable to build Hibernate SessionFactory
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: DB1] Unable to build Hibernate SessionFactory
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: SQL strings added more than once for: <schema_name>.<table_name>

yrodiere · 2022-06-13T12:25:15Z

Thanks for the precisions. A few more questions:

I solved the problem by adding the "quarkus.datasource" property.

Which one exactly? quarkus.datasource is just a prefix.
Also, I can see that you do use quarkus.datasource properties in your configuration "without the fix".

Error stack trace:

Unfortunately, that stack trace is not complete... Any chance you can look into the test report (target/surefire-reports/something.txt) and extract the full stack trace from there?

Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: SQL strings added more than once for: <schema_name>.<table_name>

This error most likely happens because two entities are bound to the same table, for some reason. I really wonder how configuring the datasource could solve that problem...

leonardowestphal · 2022-06-30T19:53:49Z

Which one exactly? quarkus.datasource is just a prefix. Also, I can see that you do use quarkus.datasource properties in your configuration "without the fix".

quarkus.datasource."DB1".jdbc.url
quarkus.datasource."DB2".jdbc.url

Unfortunately, that stack trace is not complete... Any chance you can look into the test report (target/surefire-reports/something.txt) and extract the full stack trace from there?

The stack trace is the same. I took a look at the .xml file on surefire-reports and found this:

WARN  [org.hib.eng.jdb.env.int.JdbcEnvironmentInitiator] (JPA Startup Thread: DB1) HHH000342: Could not obtain connection to query metadata: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "username"
	at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:646)
	at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:180)
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:235)
	at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
	at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:223)
	at org.postgresql.Driver.makeConnection(Driver.java:400)
	at org.postgresql.Driver.connect(Driver.java:259)
	at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:226)
	at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:535)
	at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:516)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:75)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1126)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

If there was an authentication error the application would not even run. And the login data are correct...

This error most likely happens because two entities are bound to the same table, for some reason. I really wonder how configuring the datasource could solve that problem...

I agree with you. This looks weird but...
I don't have two entities bounded to the same table. If so, the error would occur when running the application too. Maybe it's happening because I use two persistence units with the same mappings/entities (Master and Slave).

leonardowestphal · 2022-06-30T20:16:35Z

I just updated the quarkus version to 2.9.2 and the Java version to 17 and I also changed the name of the PUs (I noticed that one of them had the same name of the database schema and so I decided to change it to test). Now when I run the tests I don't have the error 'SQL strings added more than once for: <schema_name>.<table_name>' anymore.

Now when I run the tests without 'quarkus.datasource."DB1".jdbc.url' (only with %dev.quarkus.datasource."DB1".jdbc.url) I get this:

WARN  [org.hib.eng.jdb.env.int.JdbcEnvironmentInitiator] (JPA Startup Thread: DB1) HHH000342: Could not obtain connection to query metadata: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "username"
        at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:646)
        at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:180)
        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:235)
        at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
        at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:223)
        at org.postgresql.Driver.makeConnection(Driver.java:400)
        at org.postgresql.Driver.connect(Driver.java:259)
        at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:226)
        at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:535)
        at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:516)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:75)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:833)

The application still runs without error with the command 'quarkus:dev'

When I add the %test.quarkus.datasource."DB1".jdbc.url everything is ok. Now It is clear that after version 2.1.4 it is mandatory to specify this property, but the error presented made it difficult to understand/discover.

leonardowestphal · 2022-06-30T21:01:22Z

@yrodiere
I did other tests and identified that the 'SQL strings added more than once for: <schema_name>.<table_name>' error only occurs when using the persistence unit name equal to the database schema name. In my case the only difference between them was that the first letter was capitalized on PU name.

I believe that now you can identify the origin of the weird message and fix it, if necessary.

Thanks!

yrodiere · 2022-07-01T13:36:04Z

Now It is clear that after version 2.1.4 it is mandatory to specify this property, but the error presented made it difficult to understand/discover.

The JDBC URL is mandatory if you want to use your own database. In dev mode and tests, the lack of JDBC URL should not cause any problem, as Quarkus will launch a container automatically if there's no JDBC URL.

I did other tests and identified that the 'SQL strings added more than once for: <schema_name>.<table_name>' error only occurs when using the persistence unit name equal to the database schema name

This is... very, very strange. I definitely don't know how in the world this could lead to a problem, as the PU name and schema name are handled by very different parts of the codebase.

Maybe that was just a coincidence, and you changed something else in the config?

You really meant "PU name and schema name"? Not "PU name and datasource name"? I'm asking because I noticed a strange behavior when the PU name and datasource name are different: #26507

I believe that now you can identify the origin of the weird message and fix it, if necessary.

I'm sorry but no, I can't... And, believe me, I tried.

In this discussion, I'm counting three different error messages, multiple versions of Quarkus, and multiple sets of configuration properties, only one of which is complete and explicit.

I just can't put that together and build a reproducer: all I could get is the behavior I would expect (either it works, or I get a different error than you, and one that is expected considering the configuration).

If you want me to fix something, please provide a simple reproducer. If you want, you can start from my attempt:

git clone [email protected]:yrodiere/quarkus-quickstarts.git
git switch i25607-schemamanager-exception
cd hibernate-orm-quickstart

There's a script in that directory to launch postgres and initialize the databases: launch-postgres.sh.

leonardowestphal · 2022-07-04T14:01:56Z

I did some more tests to help you.

This is... very, very strange. I definitely don't know how in the world this could lead to a problem, as the PU name and schema name are handled by very different parts of the codebase.
Maybe that was just a coincidence, and you changed something else in the config?
You really meant "PU name and schema name"? Not "PU name and datasource name"? I'm asking because I noticed a strange behavior when the PU name and datasource name are different: #26507

Yes it was just a coincidence. When I changed de PU name I also changed DS name.
You're right, the problem is the same as the issue #26507

Hope this helps! Thanks for your attention.

yrodiere · 2022-07-28T10:12:11Z

Hey @leonardowestphal , can you confirm that fixing #26507 fixed all the problems you mentioned in this thread? The fix is included in Quarkus 2.11.1.

yrodiere · 2022-08-02T10:59:23Z

I got no answer, so I'll assume this was fixed; please reopen this ticket and/or ping me if it wasn't.

leonardowestphal · 2022-08-03T14:24:39Z

@yrodiere
Yes, it works!

Thanks.

quarkus-bot bot added area/hibernate-orm Hibernate ORM area/persistence OBSOLETE, DO NOT USE labels May 16, 2022

geoand added the kind/bug Something isn't working label May 17, 2022

yrodiere added the triage/needs-reproducer We are waiting for a reproducer. label Jun 9, 2022

yrodiere closed this as completed Aug 2, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Hibernate ORM SchemaManagementException when running tests #25607

Hibernate ORM SchemaManagementException when running tests #25607

leonardowestphal commented May 16, 2022 •

edited

Loading

quarkus-bot bot commented May 16, 2022

leonardowestphal commented May 16, 2022

luisnuxx commented May 22, 2022 •

edited

Loading

yrodiere commented Jun 1, 2022

yrodiere commented Jun 9, 2022

leonardowestphal commented Jun 9, 2022

yrodiere commented Jun 13, 2022

leonardowestphal commented Jun 30, 2022

leonardowestphal commented Jun 30, 2022 •

edited

Loading

leonardowestphal commented Jun 30, 2022

yrodiere commented Jul 1, 2022

leonardowestphal commented Jul 4, 2022

yrodiere commented Jul 28, 2022

yrodiere commented Aug 2, 2022

leonardowestphal commented Aug 3, 2022

Hibernate ORM SchemaManagementException when running tests #25607

Hibernate ORM SchemaManagementException when running tests #25607

Comments

leonardowestphal commented May 16, 2022 • edited Loading

quarkus-bot bot commented May 16, 2022

leonardowestphal commented May 16, 2022

luisnuxx commented May 22, 2022 • edited Loading

yrodiere commented Jun 1, 2022

yrodiere commented Jun 9, 2022

leonardowestphal commented Jun 9, 2022

yrodiere commented Jun 13, 2022

leonardowestphal commented Jun 30, 2022

leonardowestphal commented Jun 30, 2022 • edited Loading

leonardowestphal commented Jun 30, 2022

yrodiere commented Jul 1, 2022

leonardowestphal commented Jul 4, 2022

yrodiere commented Jul 28, 2022

yrodiere commented Aug 2, 2022

leonardowestphal commented Aug 3, 2022

leonardowestphal commented May 16, 2022 •

edited

Loading

luisnuxx commented May 22, 2022 •

edited

Loading

leonardowestphal commented Jun 30, 2022 •

edited

Loading