January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16017) JPA with Geometry column won't persist for MySql

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16017 ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiMjk0OD... ) Re: JPA with Geometry column won't persist for MySql ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiMjk0OD... ) Please provide a test case to reproduce this exception. The Hibernate Spatial tests for saving, updating and querying geometry objects work fine for what we have tested, so my guess is that you must be doing something “wrong” which might have worked by accident in Hibernate 5. ( https://hibernate.atlassian.net/browse/HHH-16017#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16017#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:b01baad )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16018) ClassCastException on HQL CASE/WHEN w/Entity type - SingleTableEntityPersister vs BasicValuedMapping

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16018 ( https://hibernate.atlassian.net/browse/HHH-16018?atlOrigin=eyJpIjoiNzVkMD... ) Re: ClassCastException on HQL CASE/WHEN w/Entity type - SingleTableEntityPersister vs BasicValuedMapping ( https://hibernate.atlassian.net/browse/HHH-16018?atlOrigin=eyJpIjoiNzVkMD... ) The only “bug” here is that we are not throwing a more informative exception. A case expression requires that the result arms produce a scalar result and an entity is definitely not a scalar result. The underlying SQL will have to select columns for both associations anyway. I can be convinced that this can be viewed as a nice new feature, but at the same time, I don’t see how a case when expression greatly improves anything vs. retrieving both associations as result and you doing that check in Java code. There are actually some pretty hard problems here that we would have to handle if we wanted to support this, like selecting which columns to use for rendering the expression. In a select item you want to select everything, but in a predicate, you probably want the FK/PK, but if you use different associations which have different mappings, this is turns out to become a pretty annoying problem to solve in general. We already have a bunch of code that tries to handle all possible cases of comparing two entity valued paths and that is pretty complex already because there are so many cases to consider. I think that deciding on the columns when even more paths are involved is going to be even messier. What do you mean by this worked in Hibernate 5? Can you please create a test case that reproduces this scenario? ( https://hibernate.atlassian.net/browse/HHH-16018#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16018#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:b01baad )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1933) Performance issue for validating list with 20k elements

by Marko Bekhta (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4777) Add compatibility with Elasticsearch 8.6

by Automation for Jira (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4778) Upgrade to Elasticsearch client 8.6.0

by Automation for Jira (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4778) Upgrade to Elasticsearch client 8.6.0

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4778) Upgrade to Elasticsearch client 8.6.0

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4777) Add compatibility with Elasticsearch 8.6

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4778) Upgrade to Elasticsearch client 8.6.0

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4777) Add compatibility with Elasticsearch 8.6

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4777) Add compatibility with Elasticsearch 8.6

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16019) @Where clause ignored after upgrading to Hibernate 6

by Jaehoon Lee (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16019) @Where clause ignored after upgrading to Hibernate 6

by Jaehoon Lee (JIRA)

Jaehoon Lee ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61d510f... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiN2VmNzRhNTNl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16019?atlOrigin=eyJpIjoiN2VmNz... ) HHH-16019 ( https://hibernate.atlassian.net/browse/HHH-16019?atlOrigin=eyJpIjoiN2VmNz... ) @Where clause ignored after upgrading to Hibernate 6 ( https://hibernate.atlassian.net/browse/HHH-16019?atlOrigin=eyJpIjoiN2VmNz... ) Change By: Jaehoon Lee ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61d510f... ) I am experiencing strange behavior in the process of upgrading to Hibernate 6.x. It seems {{@Where}} annotation on entity class is ignored when using with entity graph or fetch join. Despite the same entity classes and queries, wrong SQL is generated after upgrading to Hibernate 6.x, which is not what I expected. I have created a sample project to test the issue and show the situation in detail. Here is GitHub repository for the sample project: * Sample project (with Hibernate 5.6.14.Final): [ GitHub - https://github.com/ dev-jaehoonlee/hibernate-orm-demo at /tree/ hibernate-5.6|https://github.com/dev-jaehoonlee/hibernate-orm-demo/tree/h... |smart-link ] * Sample project (with Hibernate 6.1.6.Final): [ GitHub - https://github.com/ dev-jaehoonlee/hibernate-orm-demo at /tree/ hibernate-6.1|https://github.com/dev-jaehoonlee/hibernate-orm-demo/tree/h... |smart-link ] I have explained the details on discourse topic - [https://discourse.hibernate.org/t/where-clause-ignored-after-upgrading-to...] I also forked hibernate-test-case-templates repository and added test cases: [https://github.com/dev-jaehoonlee/hibernate-test-case-templates/tree/HHH-...] [orm/hibernate-orm-5/src/test/java/org/hibernate/bugs/JPAUnitTestCase.java...] and [orm/hibernate-orm-6/src/test/java/org/hibernate/bugs/JPAUnitTestCase.java...] have the same test cases, but tests are passed with Hibernate 5.6 and failed with Hibernate 6.1 ( https://hibernate.atlassian.net/browse/HHH-16019#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16019#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:b01baad )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16019) @Where clause ignored after upgrading to Hibernate 6

by Jaehoon Lee (JIRA)

Jaehoon Lee ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61d510f... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDExZDgzYTA3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16019?atlOrigin=eyJpIjoiNDExZD... ) HHH-16019 ( https://hibernate.atlassian.net/browse/HHH-16019?atlOrigin=eyJpIjoiNDExZD... ) @Where clause ignored after upgrading to Hibernate 6 ( https://hibernate.atlassian.net/browse/HHH-16019?atlOrigin=eyJpIjoiNDExZD... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Created: 10/Jan/2023 19:32 PM Priority: Major Reporter: Jaehoon Lee ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61d510f... ) I am experiencing strange behavior in the process of upgrading to Hibernate 6.x. It seems @Where annotation on entity class is ignored when using with entity graph or fetch join. Despite the same entity classes and queries, wrong SQL is generated after upgrading to Hibernate 6.x, which is not what I expected. I have created a sample project to test the issue and show the situation in detail. Here is GitHub repository for the sample project: * Sample project (with Hibernate 5.6.14.Final): GitHub - dev-jaehoonlee/hibernate-orm-demo at hibernate-5.6 ( https://github.com/dev-jaehoonlee/hibernate-orm-demo/tree/hibernate-5.6 ) * Sample project (with Hibernate 6.1.6.Final): GitHub - dev-jaehoonlee/hibernate-orm-demo at hibernate-6.1 ( https://github.com/dev-jaehoonlee/hibernate-orm-demo/tree/hibernate-6.1 ) I have explained the details on discourse topic - https://discourse.hibernate.org/t/where-clause-ignored-after-upgrading-to... ( https://discourse.hibernate.org/t/where-clause-ignored-after-upgrading-to... ) ( https://hibernate.atlassian.net/browse/HHH-16019#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16019#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:b01baad )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16018) ClassCastException on HQL CASE/WHEN w/Entity type - SingleTableEntityPersister vs BasicValuedMapping

by Kurt Gollhardt (JIRA)

Kurt Gollhardt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjY3YzJmYzE2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16018?atlOrigin=eyJpIjoiNjY3Yz... ) HHH-16018 ( https://hibernate.atlassian.net/browse/HHH-16018?atlOrigin=eyJpIjoiNjY3Yz... ) ClassCastException on HQL CASE/WHEN w/Entity type - SingleTableEntityPersister vs BasicValuedMapping ( https://hibernate.atlassian.net/browse/HHH-16018?atlOrigin=eyJpIjoiNjY3Yz... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Components: query-hql Created: 10/Jan/2023 17:38 PM Priority: Major Reporter: Kurt Gollhardt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The CaseSearchedExpression constructor casts the type parameter to BasicValuedMapping. This gets a ClassCastException when the type is a SingleTableEntityPersister. For example: select case when true then customer1 else customer2 end from TransactRecord @Entity(name = "TransactRecord" ) class TransactRecord { @JoinColumn(name = "CUSTOMER1" , nullable = true ) @ManyToOne(fetch = FetchType.EAGER) @LazyToOne(LazyToOneOption.FALSE) private CustomerRecord customer1; @JoinColumn(name = "CUSTOMER2" , nullable = true ) @ManyToOne(fetch = FetchType.EAGER) @LazyToOne(LazyToOneOption.FALSE) private CustomerRecord customer2; } @Entity(name = "CustomerRecord" ) class CustomerRecord { // ... } This worked in 5.4.22. Workaround: The Simple Case expression does not have this problem. For example: select case property when value then customer1 else customer2 end from TransactRecord ( https://hibernate.atlassian.net/browse/HHH-16018#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16018#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Fabien Seznec (JIRA)

Fabien Seznec ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5cc6397... ) *commented* on HHH-15890 ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiOGI5Mj... ) Re: springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiOGI5Mj... ) Indeed ! Everything works correctly within our projects now. I’ll raise a green flag to my development team for a migration to springboot 3 when it is released with hibernate 6.1.7+. Thank you very much ! ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16017) JPA with Geometry column won't persist for MySql

by dt pham (JIRA)

dt pham ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e14f16... ) *commented* on HHH-16017 ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiMzZmZm... ) Re: JPA with Geometry column won't persist for MySql ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiMzZmZm... ) Note that the binding parameter in working system is [ARRAY] while the binding parameter in none working system is [VARBINARY]. Both apps run again same database, mysql 8, where table has Geometry sql type column. ( https://hibernate.atlassian.net/browse/HHH-16017#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16017#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16017) JPA with Geometry column won't persist for MySql

by dt pham (JIRA)

dt pham ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e14f16... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiN2UxNDFjOWUz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiN2UxND... ) HHH-16017 ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiN2UxND... ) JPA with Geometry column won't persist for MySql ( https://hibernate.atlassian.net/browse/HHH-16017?atlOrigin=eyJpIjoiN2UxND... ) Issue Type: Bug Affects Versions: 6.1.5 Assignee: Unassigned Components: hibernate-core, hibernate-spatial Created: 10/Jan/2023 13:51 PM Environment: When migrating wildfly 24 (hibernate 5.3.20 and jdk 13) to wildfly 27 (hibernate 6.1.5 and jdk 17). Test on MySql 8.0.31. The application on wildffly 24 is working fine, but on wildfly 27 it won't persists the JPA object unless the geometry data is NULL. Stack trace: DEBUG [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (default task-7) could not execute statement [n/a]: com.mysql.cj.jdbc.exceptions.MysqlDataTruncation: Data truncation: Cannot get geometry object from data you send to the GEOMETRY field at com.networks.database.mysql(a)8.0.19 ( com.networks.database.mysql(a)8.0.19 ) //com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:104) at com.networks.database.mysql(a)8.0.19 ( com.networks.database.mysql(a)8.0.19 ) //com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:953) at com.networks.database.mysql(a)8.0.19 ( com.networks.database.mysql(a)8.0.19 ) //com.mysql.cj.jdbc.ClientPreparedStatement.executeUpdateInternal(ClientPreparedStatement.java:1092) at com.networks.database.mysql(a)8.0.19 ( com.networks.database.mysql(a)8.0.19 ) //com.mysql.cj.jdbc.ClientPreparedStatement.executeUpdateInternal(ClientPreparedStatement.java:1040) at com.networks.database.mysql(a)8.0.19 ( com.networks.database.mysql(a)8.0.19 ) //com.mysql.cj.jdbc.ClientPreparedStatement.executeLargeUpdate(ClientPreparedStatement.java:1347) at com.networks.database.mysql(a)8.0.19 ( com.networks.database.mysql(a)8.0.19 ) //com.mysql.cj.jdbc.ClientPreparedStatement.executeUpdate(ClientPreparedStatement.java:1025) at org.jboss.ironjacamar.jdbcadapters(a)1.5.9.Final ( org.jboss.ironjacamar.jdbcadapters(a)1.5.9.Final ) //org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:537) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:197) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3587) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:3449) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3864) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.action.internal.EntityUpdateAction.execute(EntityUpdateAction.java:164) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:612) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.engine.spi.ActionQueue.lambda$executeActions$1(ActionQueue.java:483) at java.base/java.util.LinkedHashMap.forEach(LinkedHashMap.java:721) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:480) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:329) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:107) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1422) at org.hibernate(a)6.1.5.Final ( org.hibernate(a)6.1.5.Final ) //org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1408) at org.jboss.as.jpa(a)27.0.1.Final ( org.jboss.as.jpa(a)27.0.1.Final ) //org.jboss.as.jpa.container.AbstractEntityManager.flush(AbstractEntityManager.java:462) at deployment.atms.ear.event-ejb.jar//com.networks.events.ManagerSSB.update(ManagerSSB.java:264) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.jboss.as.ee(a)27.0.1.Final ( org.jboss.as.ee(a)27.0.1.Final ) //org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.common(a)27.0.1.Final ( org.jboss.as.weld.common(a)27.0.1.Final ) //org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) at org.jboss.as.weld.common(a)27.0.1.Final ( org.jboss.as.weld.common(a)27.0.1.Final ) //org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89) at org.jboss.as.weld.common(a)27.0.1.Final ( org.jboss.as.weld.common(a)27.0.1.Final ) //org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102) at org.jboss.as.ee(a)27.0.1.Final ( org.jboss.as.ee(a)27.0.1.Final ) //org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.jpa(a)27.0.1.Final ( org.jboss.as.jpa(a)27.0.1.Final ) //org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee(a)27.0.1.Final ( org.jboss.as.ee(a)27.0.1.Final ) //org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee(a)27.0.1.Final ( org.jboss.as.ee(a)27.0.1.Final ) //org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:56) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:254) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:416) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:162) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.core(a)5.1.0.Final ( org.jboss.weld.core(a)5.1.0.Final ) //org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) at org.jboss.as.weld.common(a)27.0.1.Final ( org.jboss.as.weld.common(a)27.0.1.Final ) //org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.security.IdentityOutflowInterceptor.processInvocation(IdentityOutflowInterceptor.java:73) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.security.RolesAllowedInterceptor.processInvocation(RolesAllowedInterceptor.java:63) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.security.SecurityDomainInterceptor.processInvocation(SecurityDomainInterceptor.java:44) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:45) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee(a)27.0.1.Final ( org.jboss.as.ee(a)27.0.1.Final ) //org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.elytron-base(a)2.0.0.Final ( org.wildfly.security.elytron-base(a)2.0.0.Final ) //org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:633) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation(a)1.7.0.Final ( org.jboss.invocation(a)1.7.0.Final ) //org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee(a)27.0.1.Final ( org.jboss.as.ee(a)27.0.1.Final ) //org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ejb3(a)27.0.1.Final ( org.jboss.as.ejb3(a)27.0.1.Final ) //org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:257) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:499) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocation(RemotingEJBClientInterceptor.java:52) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:514) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocation(TransactionPostDiscoveryInterceptor.java:82) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:514) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocation(DiscoveryEJBClientInterceptor.java:116) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:514) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocation(NamingEJBClientInterceptor.java:69) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:514) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.lambda$handleInvocation$0(AuthenticationContextEJBClientInterceptor.java:45) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.call(AuthenticationContextEJBClientInterceptor.java:59) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.handleInvocation(AuthenticationContextEJBClientInterceptor.java:44) at org.jboss.ejb-client(a)5.0.1.Final ( org.jboss.ejb-client(a)5.0.1.Final ) //org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:514) Priority: Major Reporter: dt pham ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e14f16... ) ( https://hibernate.atlassian.net/browse/HHH-16017#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16017#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Matt Henry (JIRA)

Matt Henry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5bff329... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiOGI3Nj... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiOGI3Nj... ) V10R1 - Compatibility with the behavior of Db2 11 new-function mode. After migration to Db2 12, this value has the same result as specifying V12R1M100. ( https://www.ibm.com/docs/en/db2-for-zos/11?topic=11-db2-migration-modes ( https://www.ibm.com/docs/en/db2-for-zos/11?topic=11-db2-migration-modes ) see bottom of page) V11R1 - Compatibility with the behavior of Db2 11 new-function mode. After migration to Db2 12, this value has the same result as specifying V12R1M100. V12R1M*** (stars = function level detailed here https://www.ibm.com/docs/en/db2-for-zos/12?topic=12-db2-function-levels ( https://www.ibm.com/docs/en/db2-for-zos/12?topic=12-db2-function-levels ) ) So in the context of DB2 v12, seems V11R1 is equal to the lowest DB2 12 function level (V12R1M100), which has parity with V11. Then levels 100, 500, 501, etc add more functionality each. ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16016) HSQLDB not supported 'statement name starting with an underscore followed by a digit'

by Mehdi Eftekhari (JIRA)

Mehdi Eftekhari ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzcyMDhkNDgy... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16016?atlOrigin=eyJpIjoiMzcyMD... ) HHH-16016 ( https://hibernate.atlassian.net/browse/HHH-16016?atlOrigin=eyJpIjoiMzcyMD... ) HSQLDB not supported 'statement name starting with an underscore followed by a digit' ( https://hibernate.atlassian.net/browse/HHH-16016?atlOrigin=eyJpIjoiMzcyMD... ) Issue Type: Improvement Affects Versions: 6.1.6 Assignee: Unassigned Components: hibernate-core, query-hql Created: 10/Jan/2023 12:32 PM Environment: hibernate version: 6.1.6 hsqldb: 2.7.1 java: 11 os: win10 ---hibernate configs--- hibernate.globally_quoted_identifiers=true Priority: Major Reporter: Mehdi Eftekhari ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hibernate: select _1_0."id",_1_0."country_code",_1_0."number" from "person_mobile" _1_0 where _1_0."id"=? org.hibernate.engine.jdbc.spi.SqlExceptionHelper logExceptions ERROR: unknown token: _ in statement [select _1_0."id",_1_0."country_code",_1_0."number" from "person_mobile" _1_0 where _1_0."id"=?] 1- can i config hibernate how naming variables in generated query ? 2- can i config hibernate to quote auto generated variables like _1_0 ( https://hibernate.atlassian.net/browse/HHH-16016#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16016#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiNDdjMD... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiNDdjMD... ) So V10R1 corresponds to version 10.0, V11R1 to 11.0, V12R1 to 12.0, right? ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16015) NPE when using CompositeUserType in Hibernate 6.1.6

by Sahawut Wesaratchakit (JIRA)

Sahawut Wesaratchakit ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjU1ZDRhYmY0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16015?atlOrigin=eyJpIjoiNjU1ZD... ) HHH-16015 ( https://hibernate.atlassian.net/browse/HHH-16015?atlOrigin=eyJpIjoiNjU1ZD... ) NPE when using CompositeUserType in Hibernate 6.1.6 ( https://hibernate.atlassian.net/browse/HHH-16015?atlOrigin=eyJpIjoiNjU1ZD... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Created: 10/Jan/2023 10:10 AM Environment: Hibernate-6.1.6, Java-17, Windows-11, PostGreSQL, H2 Priority: Major Reporter: Sahawut Wesaratchakit ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I’m migrating my UserType class from Hibernate 5 to 6. As far as I understand the rules, I should use CompositeUserType because my mapped class is rather complex and encapsulates several properties to be persisted. This can’t be accomplished by UserType according to Hibernate 6’s JavaDoc. For the most part, it works. But there is one particular scenario where it can’t handle the cascading merge; I got a NullPointerException , as follows: > > > > java.lang.NullPointerException: Cannot invoke > “org.hibernate.property.access.spi.Setter.set(Object, Object)” because the > return value of > “org.hibernate.property.access.spi.PropertyAccess.getSetter()” is null > > See entire exception stack trace ( https://github.com/sahawut/hibernate6-issue/blob/master/Test%20case%202%2... ) I created a minimal sample project ( https://github.com/sahawut/hibernate6-issue ) to reproduce the problem. @beikov identified it as a bug. For your convenience, I excerpt the important code from my sample project for a quick read. Here is my VaultValue type encapsulating a piece of data securely stored in a Vault: public class VaultValue { protected String value = null; // plaintext to be persisted into a secure Vault storage protected Instant date = null; // the date when plaintext was persisted into the secure Vault storage protected Long vaultId = null; // an opaque id used to reference the plaintext persisted in the secure Vault storage protected String hashValue = null; // a hash value calculated based on the plaintext public VaultValue() {} public VaultValue(Long vaultId, String hashValue) { this.vaultId = vaultId; this.hashValue = hashValue; } public VaultValue(VaultValue src) { this.vaultId = src.vaultId; this.hashValue = src.hashValue; this.value = src.value; this.date = src.date; } public Long getVaultId() { return this.vaultId; } public String getHashValue() { return this.hashValue; } private boolean setValue(String value, Instant date) { final var newHash = hash(value); final boolean changed = !StringUtils.equals(this.hashValue, newHash); this.value = value; this.date = date; this.hashValue = newHash; return changed; } public static VaultValue setValue(VaultValue vaultValue, String value, Instant date) { VaultValue retval = (vaultValue == null ? new VaultValue() : vaultValue); retval.setValue(value, date); return retval; } public static String hash(String value) { if (value == null) return ""; return DigestUtils.sha256Hex(value.getBytes()); } @Override public boolean equals(Object o) { if (o == this) return true; if (!(o instanceof VaultValue)) return false; VaultValue other = (VaultValue)o; // For use by Hibernate dirty-checking, it is important that this test only the // values that are persisted in the database: vaultId and hashValue. if (!Objects.equals(this.vaultId, other.vaultId)) return false; if (!Objects.equals(this.hashValue, other.hashValue)) return false; return true; } @Override public int hashCode() { return Objects.hashCode(this.vaultId); } } Here is my CompositeUserType class that maps the VaultValue type: public class VaultType implements CompositeUserType<VaultValue> { public static class EmbeddableMapper { String hash; Long id; } @Override public Object getPropertyValue(VaultValue component, int property) throws HibernateException { return switch (property) { // Hibernate sorts the properties by their names alphabetically case 0 -> component.getHashValue(); case 1 -> component.getVaultId(); default -> null; }; } @Override public VaultValue instantiate(ValueAccess values, SessionFactoryImplementor sessionFactory) { final String hash = values.getValue(0, String.class); final Long id = values.getValue(1, Long.class); return new VaultValue(id, hash); } @Override public Class<?> embeddable() { return EmbeddableMapper.class; } @Override public Class<VaultValue> returnedClass() { return VaultValue.class; } @Override public boolean equals(VaultValue x, VaultValue y) { return Objects.equals(x, y); } @Override public int hashCode(VaultValue x) { return Objects.hashCode(x); } @Override public boolean isMutable() { return true; } // Yes, the VaultValue internal state may change @Override public VaultValue deepCopy(VaultValue value) { if (value == null) return null; return new VaultValue(value); } @Override public Serializable disassemble(VaultValue value) { throw new UnsupportedOperationException(); } @Override public VaultValue assemble(Serializable cached, Object owner) { throw new UnsupportedOperationException(); } @Override public VaultValue replace(VaultValue detached, VaultValue managed, Object owner) { return deepCopy(detached); } } In my model, I have two entity classes: * *Encounter* - an encounter in a healthcare setting * *Observation* - a physician’s observation of the patient An Encounter has a collection of Observations; basically, *Encounter* and *Observation* have a cascade one-to-many relation. Both the *Encounter* entity and the *Observation* entity have a property of my VaultValue class. By and large, they seem to work with Hibernate 6.1.6 (via Spring Boot 3.0.1). However, when an *Encounter* instance is re-saved after some new *Observation* instances are added to it, I get NullPointerException caused by PropertyAccessCompositeUserTypeImpl::getSetter() which always returns null. Here is the Observation entity class: @Entity public class Observation extends IdObject { @ManyToOne(fetch = FetchType.EAGER, optional = false) @JoinColumn(name = "id_encounter", nullable = false, updatable = false, foreignKey = @ForeignKey(name = "FK_observation_has_encounter")) private Encounter encounter; public void setEncounter(Encounter encounter) { this.encounter = encounter; } public Encounter getEncounter() { return this.encounter; } @Embedded @AttributeOverride(name = "id", column = @Column(name = "secure_value_id")) @AttributeOverride(name = "hash", column = @Column(name = "secure_value_hash")) @CompositeType(VaultType.class) private VaultValue secureValue = new VaultValue(); public void setSecureValue(VaultValue secureValue) { this.secureValue = secureValue; } public void setSecureValue(String value, Instant referenceDate) { secureValue = VaultValue.setValue(secureValue, StringUtils.trimToNull(value), referenceDate); } public VaultValue getSecureValue() { return this.secureValue; } } Here is the Encounter entity class: @Entity public class Encounter extends IdObject { @Embedded @AttributeOverride(name = "id", column = @Column(name = "identifier_id")) @AttributeOverride(name = "hash", column = @Column(name = "identifier_hash")) @CompositeType(VaultType.class) private VaultValue identifier = new VaultValue(); public void setIdentifier(String rawValue, Instant referenceDate) { String value = StringUtils.trimToNull(rawValue); identifier = VaultValue.setValue(identifier, value, referenceDate); } public VaultValue getIdentifier() { return this.identifier; } @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL, mappedBy = "encounter") private Set<Observation> observations = new HashSet<>(); public Set<Observation> getObservations() { return this.observations; } public void setObservations(Set<Observation> observations) { this.observations = observations; } } The following is the test code that reproduces the NullPointerException (i.e. the Test Case 2 in HibernateApplicationTests code in my minimal sample project, see the link above): @Test void saveEncounterWithoutSavingObservationsThenSaveEncounterAgain_NOT_OK() { // Create and save an Encounter. final Encounter encounter = new Encounter(); encounter.setIdentifier("Medical-Record-Number-123456", Instant.now()); mockPersistToVault(encounter.getIdentifier()); encounterRepository.save(encounter); // Create and add an Observation to the Encounter. final Observation observation = new Observation(); observation.setEncounter(encounter); encounter.getObservations().add(observation); observation.setSecureValue("triage notes including patient's private information blah blah blah...", Instant.now()); mockPersistToVault(observation.getSecureValue()); // Attempt re-saving the Encounter in order to propagate saving of Observations via one-to-many cascade. assertThatThrownBy(() -> encounterRepository.save(encounter)) .isInstanceOf(NullPointerException.class); // Why does PropertyAccessCompositeUserTypeImpl::getSetter() return null? /* encounterRepository.save(encounter); */ // desired /* assertThat(observation.getId()).isNotNull(); */ // desired } Note: * encounterRepository is an injected Spring JPA Repository * mockPersistToVault() just assigns vaultId an arbitrary number for the VaultValue argument I could work around it by saving every Observation in the collection first before re-saving the Encounter. However, this shouldn’t be necessary because I set up cascade for the one-to-many relation. In fact, I didn’t need to do so with Hibernate 5.6.14. ( https://hibernate.atlassian.net/browse/HHH-16015#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16015#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Matt Henry (JIRA)

Matt Henry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5bff329... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiYjYwZT... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiYjYwZT... ) SELECT CURRENT APPLICATION COMPATIBILITY FROM SYSIBM.SYSDUMMY1; I get 1 row with a single column: ‘V11R1’ https://www.ibm.com/docs/en/db2-for-zos/12?topic=zos-application-compatib... ( https://www.ibm.com/docs/en/db2-for-zos/12?topic=zos-application-compatib... ) ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15372) Static metamodel generator references version 2.1

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1928) Bad validator performance when adding obsolete @Validated to Java value objects

by Anatoliy Balakirev (JIRA)

Anatoliy Balakirev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c62d60... ) *commented* on HV-1928 ( https://hibernate.atlassian.net/browse/HV-1928?atlOrigin=eyJpIjoiZGJhMzgz... ) Re: Bad validator performance when adding obsolete @Validated to Java value objects ( https://hibernate.atlassian.net/browse/HV-1928?atlOrigin=eyJpIjoiZGJhMzgz... ) Just to give more use-cases to this issue: we now have exactly the same problem for beans, generated by the “openapi-generator-maven-plugin”. I’ve described it here: https://hibernate.atlassian.net/browse/HV-1933 ( https://hibernate.atlassian.net/browse/HV-1933 ) And in our case the fix is not so trivial, as it will have to go to that plugin eventually. ( https://hibernate.atlassian.net/browse/HV-1928#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1928#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1933) Performance issue for validating list with 20k elements

by Anatoliy Balakirev (JIRA)

Anatoliy Balakirev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c62d60... ) *commented* on HV-1933 ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiM2RmNDQ4... ) Re: Performance issue for validating list with 20k elements ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiM2RmNDQ4... ) Hi Marko. Thanks for the hint! Indeed, when I remove those not needed @Valid annotations - it gets much much faster. Goes all the way down to the sub-second range (around 700ms) from 20-50 seconds and that’s even without https://hibernate.atlassian.net/browse/HV-1831 ( https://hibernate.atlassian.net/browse/HV-1831 )... Now I only need to figure out how to make openapi-generator-maven-plugin not to generate those 🙂 But that’s a separate story anyway. Thanks for the help and I guess this ticket can be closed as duplicated then. ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16004) Downcasting with CriteriaBuilder.treat causes ClassCastException

by Roberts Z (JIRA)

Roberts Z ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63bc113... ) *commented* on HHH-16004 ( https://hibernate.atlassian.net/browse/HHH-16004?atlOrigin=eyJpIjoiMWNmMj... ) Re: Downcasting with CriteriaBuilder.treat causes ClassCastException ( https://hibernate.atlassian.net/browse/HHH-16004?atlOrigin=eyJpIjoiMWNmMj... ) @Marco Belladelli Thank You! Feel free to close this. ( https://hibernate.atlassian.net/browse/HHH-16004#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16004#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16004) Downcasting with CriteriaBuilder.treat causes ClassCastException

by Marco Belladelli (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16004) Downcasting with CriteriaBuilder.treat causes ClassCastException

by Marco Belladelli (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16014) Querying property from treated path causes IllegalArgumentException: Already registered a copy

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmI5MmU0ZDcx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16014?atlOrigin=eyJpIjoiZmI5Mm... ) HHH-16014 ( https://hibernate.atlassian.net/browse/HHH-16014?atlOrigin=eyJpIjoiZmI5Mm... ) Querying property from treated path causes IllegalArgumentException: Already registered a copy ( https://hibernate.atlassian.net/browse/HHH-16014?atlOrigin=eyJpIjoiZmI5Mm... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) Components: query-criteria Created: 10/Jan/2023 07:41 AM Priority: Major Reporter: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) Querying a property of a Path created by the treat method causes an Exception to be thrown. Here’s an example of a Criteria Query that triggers the problem: Path<LocalTerm> asLocalTerm = cb.treat( root.get( "term" ), LocalTerm.class ); criteria.select( root ).where( cb.equal( asLocalTerm.get( "property" ), value ) ); And here’s the stack trace: java.lang.IllegalArgumentException: Already registered a copy: SqmEntityValuedSimplePath(treat(org.hibernate.orm.test.jpa.criteria.TreatTablePerClassTest$Linkage(27365580293082).term as org.hibernate.orm.test.jpa.criteria.TreatTablePerClassTest$LocalTerm).language) at org.hibernate.query.sqm.tree.SqmCopyContext$1.registerCopy(SqmCopyContext.java:33) at org.hibernate.query.sqm.tree.domain.SqmEntityValuedSimplePath.copy(SqmEntityValuedSimplePath.java:37) at org.hibernate.query.sqm.tree.domain.SqmEntityValuedSimplePath.copy(SqmEntityValuedSimplePath.java:21) at org.hibernate.query.sqm.tree.predicate.SqmComparisonPredicate.copy(SqmComparisonPredicate.java:69) at org.hibernate.query.sqm.tree.predicate.SqmComparisonPredicate.copy(SqmComparisonPredicate.java:20) at org.hibernate.query.sqm.tree.predicate.SqmWhereClause.copy(SqmWhereClause.java:33) at org.hibernate.query.sqm.tree.select.SqmQuerySpec.copy(SqmQuerySpec.java:104) at org.hibernate.query.sqm.tree.select.SqmQuerySpec.copy(SqmQuerySpec.java:53) at org.hibernate.query.sqm.tree.select.SqmSelectStatement.copy(SqmSelectStatement.java:131) at org.hibernate.query.sqm.tree.select.SqmSelectStatement.copy(SqmSelectStatement.java:42) at org.hibernate.query.sqm.internal.QuerySqmImpl.<init>(QuerySqmImpl.java:227) at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:1295) at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:181) The issue appears to be caused by the copy method of the treatedPath.get("property") object: here, the left-hand side, which is the {{treat}}ed path, causes another copy of the property to be triggered while the first one was still being processed and not registered. ( https://hibernate.atlassian.net/browse/HHH-16014#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16014#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1933) Performance issue for validating list with 20k elements

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HV-1933 ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiMDRmMmY1... ) Re: Performance issue for validating list with 20k elements ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiMDRmMmY1... ) hey, Anatoliy Balakirev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c62d60... ) thanks for reporting the issue and providing the code examples. Please see linked issues - https://hibernate.atlassian.net/browse/HV-1831 ( https://hibernate.atlassian.net/browse/HV-1831 ) and https://hibernate.atlassian.net/browse/HV-1928 ( https://hibernate.atlassian.net/browse/HV-1928 ) Looks like in your case you have a combination of both. You don’t really need to have @Valid unless you expect to do cascading validation (so places like private @Valid String currencyCode; shouldn’t use @Valid ). And well the fact that you have a huge list of objects for cascading degrades the performance ( https://hibernate.atlassian.net/browse/HV-1831 ( https://hibernate.atlassian.net/browse/HV-1831 ) should address that part) ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1933) Performance issue for validating list with 20k elements

by Anatoliy Balakirev (JIRA)

Anatoliy Balakirev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c62d60... ) *commented* on HV-1933 ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiODE1YWIy... ) Re: Performance issue for validating list with 20k elements ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiODE1YWIy... ) It could also be that this is actually an expected performance and there is not much we can do here, but I would at least like to get that feedback then, to make a decision on our side whether we should use Hibernate Validator to validate such a big objects or not. ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16013) Lazy loading fails with "Generation of HibernateProxy instances at runtime is not allowed" when run as native

by jschauder (JIRA)

jschauder ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61eece9... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTlhMjQ1OWJm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16013?atlOrigin=eyJpIjoiNTlhMj... ) HHH-16013 ( https://hibernate.atlassian.net/browse/HHH-16013?atlOrigin=eyJpIjoiNTlhMj... ) Lazy loading fails with "Generation of HibernateProxy instances at runtime is not allowed" when run as native ( https://hibernate.atlassian.net/browse/HHH-16013?atlOrigin=eyJpIjoiNTlhMj... ) Issue Type: Bug Assignee: Unassigned Created: 10/Jan/2023 06:44 AM Priority: Major Reporter: jschauder ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61eece9... ) Reproducer code: https://github.com/theotherp/reproduce-bytecodeprovider-none ( https://github.com/theotherp/reproduce-bytecodeprovider-none ) (see http://readme.md ( http://readme.md ) ) In a Spring app compiled with Graalvm 22.3.0 loading an entity with a @OneToOne(fetch = FetchType.LAZY) fails with the following stack trace: 2023-01-06T09:56:16.246+01:00 ERROR 152864 --- [nio-8080-exec-3] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: org.springframework.orm.jpa.JpaSystemException: Generation of HibernateProxy instances at runtime is not allowed when the configure d BytecodeProvider is 'none'; your model requires a more advanced BytecodeProvider to be enabled.] with root cause org.hibernate.HibernateException: Generation of HibernateProxy instances at runtime is not allowed when the configured BytecodeProvider is 'none'; your model requires a more advanced BytecodeProvider to be enabled. at org.hibernate.bytecode.internal.none.DisallowedProxyFactory.getProxy(DisallowedProxyFactory.java:34) ~[na:na] at org.hibernate.persister.entity.AbstractEntityPersister.createProxy(AbstractEntityPersister.java:5001) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.hibernate.event.internal.DefaultLoadEventListener.createProxy(DefaultLoadEventListener.java:463) ~[na:na] at org.hibernate.event.internal.DefaultLoadEventListener.createProxyIfNecessary(DefaultLoadEventListener.java:453) ~[na:na] at org.hibernate.event.internal.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:357) ~[na:na] at org.hibernate.event.internal.DefaultLoadEventListener.doOnLoad(DefaultLoadEventListener.java:113) ~[na:na] at org.hibernate.event.internal.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:75) ~[na:na] at org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:118) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.hibernate.internal.SessionImpl.fireLoadNoChecks(SessionImpl.java:1244) ~[na:na] at org.hibernate.internal.SessionImpl.internalLoad(SessionImpl.java:1097) ~[na:na] at org.hibernate.sql.results.graph.entity.internal.EntityDelayedFetchInitializer.resolveInstance(EntityDelayedFetchInitializer.java:164) ~[na:na] at org.hibernate.sql.results.internal.StandardRowReader.coordinateInitializers(StandardRowReader.java:147) ~[na:na] at org.hibernate.sql.results.internal.StandardRowReader.readRow(StandardRowReader.java:97) ~[na:na] at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:198) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:33) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:443) ~[na:na] at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:166) ~[na:na] at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:91) ~[na:na] at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:31) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.lambda$new$0(ConcreteSqmSelectQueryPlan.java:113) ~[na:na] at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:335) ~[na:na] at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:276) ~[na:na] at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:571) ~[na:na] at org.hibernate.query.spi.AbstractSelectionQuery.list(AbstractSelectionQuery.java:363) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.hibernate.query.sqm.internal.QuerySqmImpl.list(QuerySqmImpl.java:1073) ~[na:na] at org.hibernate.query.Query.getResultList(Query.java:94) ~[reproduce-bytecodeprovider-none.exe:6.1.6.Final] at org.springframework.data.jpa.repository.support.SimpleJpaRepository.findAll(SimpleJpaRepository.java:405) ~[reproduce-bytecodeprovider-none.exe:3.0.0] at java.base@17.0.5/java.lang.reflect.Method.invoke(Method.java:568) ~[reproduce-bytecodeprovider-none.exe:na] at org.springframework.data.repository.core.support.RepositoryMethodInvoker$RepositoryFragmentMethodInvoker.lambda$new$0(RepositoryMethodInvoker.java:288) ~[na:na] at org.springframework.data.repository.core.support.RepositoryMethodInvoker.doInvoke(RepositoryMethodInvoker.java:136) ~[reproduce-bytecodeprovider-none.exe:3.0.0] at org.springframework.data.repository.core.support.RepositoryMethodInvoker.invoke(RepositoryMethodInvoker.java:120) ~[reproduce-bytecodeprovider-none.exe:3.0.0] at org.springframework.data.repository.core.support.RepositoryComposition$RepositoryFragments.invoke(RepositoryComposition.java:516) ~[reproduce-bytecodeprovider-none.exe:3.0.0] at org.springframework.data.repository.core.support.RepositoryComposition.invoke(RepositoryComposition.java:285) ~[na:na] at org.springframework.data.repository.core.support.RepositoryFactorySupport$ImplementationMethodExecutionInterceptor.invoke(RepositoryFactorySupport.java:628) ~[na:na] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.doInvoke(QueryExecutorMethodInterceptor.java:168) ~[na:na] at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.invoke(QueryExecutorMethodInterceptor.java:143) ~[na:na] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.data.projection.DefaultMethodInvokingMethodInterceptor.invoke(DefaultMethodInvokingMethodInterceptor.java:77) ~[na:na] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123) ~[na:na] at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:137) ~[na:na] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor$CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:163) ~[na:na] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97) ~[na:na] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:218) ~[na:na] at jdk.proxy4/jdk.proxy4.$Proxy48.findAll(Unknown Source) ~[na:na] at com.example.reproducebytecodeprovidernone.EntityHandler.loadById(EntityHandler.java:25) ~[reproduce-bytecodeprovider-none.exe:na] at com.example.reproducebytecodeprovidernone.RestController.load(RestController.java:22) ~[reproduce-bytecodeprovider-none.exe:na] at java.base@17.0.5/java.lang.reflect.Method.invoke(Method.java:568) ~[reproduce-bytecodeprovider-none.exe:na] at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:207) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:152) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:117) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:884) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:797) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1080) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:973) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1010) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:902) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:705) ~[reproduce-bytecodeprovider-none.exe:6.0] at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:884) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:814) ~[reproduce-bytecodeprovider-none.exe:6.0] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:223) ~[na:na] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[na:na] at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[reproduce-bytecodeprovider-none.exe:10.1.4] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) ~[na:na] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[na:na] at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) ~[na:na] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[na:na] at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) ~[na:na] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[na:na] at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116) ~[reproduce-bytecodeprovider-none.exe:6.0.3] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) ~[na:na] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[na:na] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:177) ~[na:na] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) ~[na:na] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542) ~[reproduce-bytecodeprovider-none.exe:10.1.4] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:119) ~[na:na] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) ~[reproduce-bytecodeprovider-none.exe:10.1.4] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) ~[na:na] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:357) ~[na:na] at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:400) ~[na:na] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) ~[reproduce-bytecodeprovider-none.exe:10.1.4] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:859) ~[na:na] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1734) ~[na:na] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[reproduce-bytecodeprovider-none.exe:10.1.4] at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[na:na] at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[na:na] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[na:na] at java.base@17.0.5/java.lang.Thread.run(Thread.java:833) ~[reproduce-bytecodeprovider-none.exe:na] at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:775) ~[reproduce-bytecodeprovider-none.exe:na] at org.graalvm.nativeimage.builder/com.oracle.svm.core.windows.WindowsPlatformThreads.osThreadStartRoutine(WindowsPlatformThreads.java:178) ~[na:na] Related Spring issue: https://github.com/spring-projects/spring-framework/issues/29779 ( https://github.com/spring-projects/spring-framework/issues/29779 ) Related issue based on Quarkus: HHH-13804 ( https://hibernate.atlassian.net/browse/HHH-13804 ) Closed ( https://hibernate.atlassian.net/browse/HHH-16013#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16013#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1933) Performance issue for validating list with 20k elements

by Anatoliy Balakirev (JIRA)

Anatoliy Balakirev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c62d60... ) *created* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiYzJmM2FiMWUyZ... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiYzJmM2Fi... ) HV-1933 ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiYzJmM2Fi... ) Performance issue for validating list with 20k elements ( https://hibernate.atlassian.net/browse/HV-1933?atlOrigin=eyJpIjoiYzJmM2Fi... ) Issue Type: Bug Affects Versions: 8.0.0.Final Assignee: Unassigned Components: performance, validators Created: 10/Jan/2023 06:29 AM Priority: Major Reporter: Anatoliy Balakirev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c62d60... ) We have a PUT REST endpoint, which accepts an autogenerated object, which is in fact a list of objects. We send a request there, which contains around 23k of elements. Elements in that list have a couple of concrete implementations, each has a couple of required fields and a list with a couple more elements of the same type. When hibernate validator is enabled on that endpoint - it takes somewhere between 30 and 50 seconds to validate everything. When I replace that validation with manually written methods - it takes around 0.5 seconds to validate the same. The sample project to reproduce this is here: https://github.com/anatoliy-balakirev/hibernate_validator_performance_issue ( https://github.com/anatoliy-balakirev/hibernate_validator_performance_issue ) If you are on Linux, just run the following command in the root of the project (make sure your JAVA_HOME points to Java 17): ./mvnw clean test Or this on Windows: ./mvnw.cmd clean test And you’ll see these logs: 2023-01-10T15:17:32.316+01:00 INFO 18248 --- [ main] com.example.demo.DemoControllerTest : Sending '/endpoint_with_explicit_validation' request... 2023-01-10T15:17:32.643+01:00 INFO 18248 --- [o-auto-1-exec-1] com.example.demo.DemoFilter : Got into filter 2023-01-10T15:17:33.419+01:00 INFO 18248 --- [o-auto-1-exec-1] com.example.demo.DemoController : Got into the controller with explicit validation, amount of elements in the request: 23489 2023-01-10T15:17:33.503+01:00 INFO 18248 --- [ main] com.example.demo.DemoControllerTest : It took 1187ms to execute the '/endpoint_with_explicit_validation' request 2023-01-10T15:17:33.572+01:00 INFO 18248 --- [ main] com.example.demo.DemoControllerTest : Sending '/endpoint_with_validation' request... 2023-01-10T15:17:33.607+01:00 INFO 18248 --- [o-auto-1-exec-2] com.example.demo.DemoFilter : Got into filter 2023-01-10T15:18:09.510+01:00 INFO 18248 --- [o-auto-1-exec-2] com.example.demo.DemoController : Got into the controller with validation, amount of elements in the request: 23489 2023-01-10T15:18:09.512+01:00 INFO 18248 --- [ main] com.example.demo.DemoControllerTest : It took 35940ms to execute the '/endpoint_with_validation' request 2023-01-10T15:18:09.534+01:00 INFO 18248 --- [ main] com.example.demo.DemoControllerTest : Sending '/endpoint_without_validation' request... 2023-01-10T15:18:09.584+01:00 INFO 18248 --- [o-auto-1-exec-3] com.example.demo.DemoFilter : Got into filter 2023-01-10T15:18:09.637+01:00 INFO 18248 --- [o-auto-1-exec-3] com.example.demo.DemoController : Got into the controller without validation, amount of elements in the request: 23489 2023-01-10T15:18:09.638+01:00 INFO 18248 --- [ main] com.example.demo.DemoControllerTest : It took 104ms to execute the '/endpoint_without_validation' request Which are basically about running three tests: * endpoint_with_explicit_validation - validation is done with manually written method * endpoint_with_validation - validation is done using Hibernate Validator * endpoint_without_validation - no validation at all If you want to see what exactly is being validated - uncomment this line: https://github.com/anatoliy-balakirev/hibernate_validator_performance_iss... ( https://github.com/anatoliy-balakirev/hibernate_validator_performance_iss... ) I’m using the latest Spring Boot version (3.0.1), Java 17.0.5 (Amazon Corretto) and Maven 3.8.6 P.S. I’m not sure if this should be a Bug or rather an Improvement, so left the default one there. ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1933#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16010) DefaultEvictEventListener calls handleEviction with swapped parameters

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16010 ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiOGI1ZD... ) Re: DefaultEvictEventListener calls handleEviction with swapped parameters ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiOGI1ZD... ) Fixed. ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4756) Add TCK tests against more timezones

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4756 ( https://hibernate.atlassian.net/browse/HSEARCH-4756?atlOrigin=eyJpIjoiY2N... ) Re: Add TCK tests against more timezones ( https://hibernate.atlassian.net/browse/HSEARCH-4756?atlOrigin=eyJpIjoiY2N... ) Using `ZoneId.getAvailableZoneIds()` doesn't really work as it brings back the "problematic timezones" (see linked PR for details). ( https://hibernate.atlassian.net/browse/HSEARCH-4756#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4756#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15996) Develop an abstraction for Annotation in annotation processing

by Steve Ebersole (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15996) Develop an abstraction over Annotation for annotation processing

by Steve Ebersole (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16012) Develop an abstraction for domain model Class refs

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmJkYTkzMzkz... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16012?atlOrigin=eyJpIjoiYmJkYT... ) HHH-16012 ( https://hibernate.atlassian.net/browse/HHH-16012?atlOrigin=eyJpIjoiYmJkYT... ) Develop an abstraction for domain model Class refs ( https://hibernate.atlassian.net/browse/HHH-16012?atlOrigin=eyJpIjoiYmJkYT... ) Issue Type: Improvement Assignee: Unassigned Created: 10/Jan/2023 06:09 AM Priority: Major Reporter: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When processing a domain model to build the metamodels, Hibernate needs to be careful about loading Class references. This is part of the purpose of HCANN. However, HCANN has a huge drawback in that it is not able to handle models which do not have a 1-1 correspondence between ManagedType and Class (dynamic models and `entity-name mappings). Thus far, Hibernate has only supported either of those features through hbm.xml mappings. Since hbm.xml has been deprecated and its “extensions” moved into a orm.xml extension XSD, we need to start supporting those features in “annotation processing”. ( https://hibernate.atlassian.net/browse/HHH-16012#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16012#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15996) Create an abstraction over Annotation for annotation processing

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmMzY2JmZWI2... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15996?atlOrigin=eyJpIjoiMmMzY2... ) HHH-15996 ( https://hibernate.atlassian.net/browse/HHH-15996?atlOrigin=eyJpIjoiMmMzY2... ) Create an abstraction over Annotation for annotation processing ( https://hibernate.atlassian.net/browse/HHH-15996?atlOrigin=eyJpIjoiMmMzY2... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) At the moment, annotation processing uses HCANN. HCANN provides an abstraction from , however, does not play well with models where there is not a 1-1 correspondence between managed-type and Class . Initially, the domain thought was to reuse HCANN’s model abstraction classes (XClass , XProperty, etc) but exposes {{Annotation}} directly build them within ORM itself for these cases. However, those classes are not very good at modeling these concepts at the moment and would require changes to HCANN. Ultimately Relatedly, we ultimately want to move away migrate from HCANN to use Jandex for reading the annotation details. Jandex uses also exposes abstraction over Class - {{ClassInfo}}, etc. It also exposes an abstraction from {{Annotation}} in the form of {{AnnotationInstance}}. Ultimately this move to Jandex will require lots of changes to that code. {{org.hibernate.boot.model.source}} was developed as an abstraction over the source Given all of mapping information - annotations that , {{orm.xml}}, {{hbm.xml}} with the initial intent of unifying the processing of mapping sources. This better solution there is already how {{hbm to create an abstraction in ORM itself. xml}} is processed. This work would apply that abstraction can be used to annotations and {{orm.xml}} processing as well. The approach has benefits in addition to not only abstract the processing unification, such as - # Avoiding use Class information but also the source of library APIs in processing that Class information (HCANN v. Ultimately we want to move to Jandex over HCANN for annotation consumption - see ). That work will be done under [https://hibernate.atlassian.net/browse/HHH- 9489 15698 |https://hibernate.atlassian.net/browse/HHH- 9489 15698 |smart-link]. Using this abstraction will make that migration much simpler. # Allows support for both dynamic models (MAP mode) and {{entity-name}} models. This is important for deprecation of {{hbm.xml}} in favor of annotations / {{orm.xml}} - see [https://hibernate.atlassian.net/browse/HHH- 15698 15997 |https://hibernate.atlassian.net/browse/HHH- 15698 15997 |smart-link]. Given that we will be abstracting the managed-types, we also have an opportunity to decide about how to deal with annotations. Specifically, whether we want to continue using {{Annotation}} from HCANN or use an abstraction. This issue is about creating that abstraction. ( https://hibernate.atlassian.net/browse/HHH-15996#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15996#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15996) Create an abstraction over Annotation for annotation processing

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTM5ZDQ4MWM0... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15996?atlOrigin=eyJpIjoiYTM5ZD... ) HHH-15996 ( https://hibernate.atlassian.net/browse/HHH-15996?atlOrigin=eyJpIjoiYTM5ZD... ) Create an abstraction over Annotation for annotation processing ( https://hibernate.atlassian.net/browse/HHH-15996?atlOrigin=eyJpIjoiYTM5ZD... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) At the moment, annotation processing uses HCANN. HCANN provides an abstraction from the domain model, but exposes {{ Annotation}} directly. Ultimately we want to move away from HCANN to use Jandex for reading the annotation details. Jandex uses an abstraction from {{Annotation}} in the form of {{AnnotationInstance}}. Ultimately this move to Jandex will require lots of changes to that code. {{ org.hibernate.boot.model.source}} was developed as an abstraction over the source of mapping information - annotations, {{orm.xml}}, {{hbm.xml}} with the initial intent of unifying the processing of mapping sources. This is already how {{hbm.xml}} is processed. This work would apply that to annotations and {{orm.xml}} processing as well. The approach has benefits in addition to the processing unification, such as - # Avoiding use of library APIs in processing. Ultimately we want to move to Jandex over HCANN for annotation consumption - see [https://hibernate.atlassian.net/browse/HHH-9489|https://hibernate.atlassi... this abstraction will make that migration much simpler. # Allows support for both dynamic models (MAP mode) and {{entity-name}} models. This is important for deprecation of {{hbm.xml}} in favor of annotations / {{orm.xml}} - see [https://hibernate.atlassian.net/browse/HHH-15698|https://hibernate.atlass...]. ( https://hibernate.atlassian.net/browse/HHH-15996#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15996#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15996) Create an abstraction over Annotation for annotation processing

by Steve Ebersole (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15996) Create an abstraction Annotation for annotation processing

by Steve Ebersole (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16010) DefaultEvictEventListener calls handleEviction with swapped parameters

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16010 ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiMzRiZT... ) Re: DefaultEvictEventListener calls handleEviction with swapped parameters ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiMzRiZT... ) So it seems that this was basically always broken. Anyway, I have proposed a fix to that issue and another one I spotted by just reviewing all callers of that SPI. ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16011) HQL Enum literals don't work for inner class enums

by Kurt Gollhardt (JIRA)

Kurt Gollhardt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzJmODAxMzA3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16011?atlOrigin=eyJpIjoiYzJmOD... ) HHH-16011 ( https://hibernate.atlassian.net/browse/HHH-16011?atlOrigin=eyJpIjoiYzJmOD... ) HQL Enum literals don't work for inner class enums ( https://hibernate.atlassian.net/browse/HHH-16011?atlOrigin=eyJpIjoiYzJmOD... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Components: query-hql Created: 10/Jan/2023 03:16 AM Priority: Major Reporter: Kurt Gollhardt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When an enum literal is used in a conditional expression in an HQL query and the enum is an inner class, it fails to find the enum class by name and gives a “SemanticException: Could not interpret path expression”. Given an enum InnerEnum with a value named FOO , in the class file OuterClass , in package path.to.package , it tries to do a Class.forName for “path.to.package.OuterClass.InnerEnum” instead of “path.to.package.OuterClass$InnerEnum”. It works fine if the enum is a top-level class. It also works if the enum value is passed as a (named) parameter instead of used inline as a literal. ( https://hibernate.atlassian.net/browse/HHH-16011#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16011#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4775) Improve source code compatibility of Hibernate Search with Hibernate ORM 6.2

by Yoann Rodière (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4768) Fix JavaModulePathTest with ORM 6.2

by Automation for Jira (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4772) Add failsafe to prevent log flooding for mass indexing with lots of non-critical failures

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4772 ( https://hibernate.atlassian.net/browse/HSEARCH-4772?atlOrigin=eyJpIjoiYWJ... ) Re: Add failsafe to prevent log flooding for mass indexing with lots of non-critical failures ( https://hibernate.atlassian.net/browse/HSEARCH-4772?atlOrigin=eyJpIjoiYWJ... ) Yes that makes sense. ( https://hibernate.atlassian.net/browse/HSEARCH-4772#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4772#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16010) DefaultEvictEventListener calls handleEviction with swapped parameters

by Gavin King (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16010) DefaultEvictEventListener calls handleEviction with swapped parameters

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16010 ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiNTQ4Nj... ) Re: DefaultEvictEventListener calls handleEviction with swapped parameters ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiNTQ4Nj... ) > > > > Looks like this was broken by the change of IDs from Serializable to > Object. > > Actually it looks like the order was already reversed before that change. Commit 8de46167 did not change the order of the arguments. But anyway I will take a look. ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4772) Add failsafe to prevent log flooding for mass indexing with lots of non-critical failures

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4772 ( https://hibernate.atlassian.net/browse/HSEARCH-4772?atlOrigin=eyJpIjoiNWE... ) Re: Add failsafe to prevent log flooding for mass indexing with lots of non-critical failures ( https://hibernate.atlassian.net/browse/HSEARCH-4772?atlOrigin=eyJpIjoiNWE... ) I’ve been thinking about this one … I guess if there are multiple types indexed at the time, then it would be helpful to record the first N failures for a type; otherwise, we could end up telling the user just about one type while the remaining ones also have problems? In other words - have a limit of messages per BatchIndexingWorkspace. ( https://hibernate.atlassian.net/browse/HSEARCH-4772#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4772#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16010) DefaultEvictEventListener calls handleEviction with swapped parameters

by Kurt Gollhardt (JIRA)

Kurt Gollhardt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzIxYjFhYzNk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiYzIxYj... ) HHH-16010 ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiYzIxYj... ) DefaultEvictEventListener calls handleEviction with swapped parameters ( https://hibernate.atlassian.net/browse/HHH-16010?atlOrigin=eyJpIjoiYzIxYj... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Components: hibernate-core Created: 10/Jan/2023 02:09 AM Priority: Major Reporter: Kurt Gollhardt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Original estimate: 0.5h Remaining Estimate: 0.5h Looks like this was broken by the change of IDs from Serializable to Object. The order of parameters to NaturalIdResolutions::handleEviction was changed. The call from DefaultEvictEventListener was also changed, but incorrectly. The first two parameters (should be id, object) are swapped (object, id). The compiler doesn’t catch this because they’re now both of type Object. This eventually results in the equals() method of any object already in the cache to be called with the ID of the object being evicted, rather than the object itself, and so findCachedNaturalIdById never finds anything, and removeResolution doesn’t remove the naturalId from the cache. I don’t know what the implications are of leaving a “dangling reference” like this in the cache (presumably discarded once the session is closed). ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16010#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15647) Subselect with long parameter wrongly cast to bigint for MySQL

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15866) Hibernate validation fails when OneToMany refers to fereign key in embeddable object and is marked as nullable false

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15957) Hibernate 6.1.6 Infinite Recursion/StackOverflow Using DB2 Custom Dialect

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15957) Hibernate 6.1.6 Infinite Recursion/StackOverflow Using DB2 Custom Dialect

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1932) Incomplete @Positive annotation's default message in fr

by Guillaume Smet (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1932) Incomplete @Positive annotation's default message in fr

by Guillaume Smet (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiZjIzMj... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiZjIzMj... ) >Hibernate doesn’t seem to be aware of the compatibility setting. Can you tell us how to query this compatibility setting? Then we can add code to make sure we respect that. >To overcome this, I attempted to extend both DB2Dialect and DB2zDialect to override the getVersion() method That’s the right approach to achieve what you are seeking. https://hibernate.atlassian.net/browse/HHH-15957 ( https://hibernate.atlassian.net/browse/HHH-15957 ) will be addressed shortly, so then this should work fine. Don’t worry about the driver, it’s an issue on our side. It would be great though if you could help us figure out how to handle these compatibility modes though. Please post the SQL query to fetch the compatibility mode setting and also the response/resultset that you are getting. ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15890 ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiYTBkOT... ) Re: springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiYTBkOT... ) We were able to reproducer the StackOverflow and we are now certain that https://hibernate.atlassian.net/browse/HHH-15957 ( https://hibernate.atlassian.net/browse/HHH-15957 ) is the reason for this issue, so please track that issue for further info. ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15647) Subselect with long parameter wrongly cast to bigint for MySQL

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15957) Hibernate 6.1.6 Infinite Recursion/StackOverflow Using DB2 Custom Dialect

by Marco Belladelli (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15957) Hibernate 6.1.6 Infinite Recursion/StackOverflow Using DB2 Custom Dialect

by Marco Belladelli (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15890 ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiY2QyYz... ) Re: springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiY2QyYz... ) I think this might be related to https://hibernate.atlassian.net/browse/HHH-15957 ( https://hibernate.atlassian.net/browse/HHH-15957 ) ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15984 ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiNzdiNj... ) Re: Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiNzdiNj... ) Maybe you can attach a reproducer that uses just JDBC with the same query to show the error? ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15230) Orphans not removed if they have been created in the current session

by Alexander Schwartz (JIRA)

Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) *commented* on HHH-15230 ( https://hibernate.atlassian.net/browse/HHH-15230?atlOrigin=eyJpIjoiMzVlYT... ) Re: Orphans not removed if they have been created in the current session ( https://hibernate.atlassian.net/browse/HHH-15230?atlOrigin=eyJpIjoiMzVlYT... ) There is now a failing test case build with the test-case template: https://github.com/ahus1/hibernate-test-case-templates/tree/is-HHH-15230-... ( https://github.com/ahus1/hibernate-test-case-templates/tree/is-HHH-15230-... ) It shows that this problem still exists in Hibernate 6.1.6.Final ( https://hibernate.atlassian.net/browse/HHH-15230#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15230#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Matt Henry (JIRA)

Matt Henry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5bff329... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiODk1ZD... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiODk1ZD... ) I also wonder.. could my issue potentially be related to using the default driver that Spring Boot’s project generator uses? We’ve been using it with no issues for at least a couple years now. <dependency> <groupId> com.ibm.db2 </groupId> <artifactId> jcc </artifactId> <version> 11.5.8.0 </version> </dependency> Would make sense.. since LUW does not have the Application Compatibility feature. Will try switching to the driver teams used to use. ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Matt Henry (JIRA)

Matt Henry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5bff329... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiYTg0NT... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiYTg0NT... ) The Application Compatibility is set to V11R1 on the server, so it does now allow me to run SET CURRENT APPLICATION COMPATIBILITY = 'V12R1'; unfortunately. I met with my DBAs and they agree it should be updated but in an enterprise environment things take forever. Hoping I can figure something out on the Hibernate side in the meantime. ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:cca7326 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15955) Hibernate 6.1.6 Never Uses LimitHandler w/ DB2

by Matt Henry (JIRA)

Matt Henry ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5bff329... ) *commented* on HHH-15955 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiZWExNj... ) Re: Hibernate 6.1.6 Never Uses LimitHandler w/ DB2 ( https://hibernate.atlassian.net/browse/HHH-15955?atlOrigin=eyJpIjoiZWExNj... ) Thanks for the reply @ChristianBeikov. That’s good to know that the LimitHandler is only for native queries. We are running DB2 z/OS, but our DBAs have the Application Compatibility level set to V11R1 which prevents us from using the offset keyword. Hibernate doesn’t seem to be aware of the compatibility setting. To overcome this, I attempted to extend both DB2Dialect and DB2zDialect to override the getVersion() method but it causes an infinite recursion: https://hibernate.atlassian.net/browse/HHH-15957 ( https://hibernate.atlassian.net/browse/HHH-15957 ) This is our main blocker for completely embracing the new Spring Boot 3 🙂 ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15955#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16006) Implement an "additional mapping" contributor SPI

by Steve Ebersole (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Fabien Seznec (JIRA)

Fabien Seznec ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5cc6397... ) *commented* on HHH-15890 ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiZDJkZj... ) Re: springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiZDJkZj... ) The stackoverflow on org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions occurs when using any paged request (org.springframework.data.repository.PagingAndSortingRepository.findAll(Pageable pageable)). I feel like it is related to the fix. If it is not the case, tell me I’ll file another issue. ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Fabien Seznec (JIRA)

Fabien Seznec ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5cc6397... ) *commented* on HHH-15890 ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiNzgzNT... ) Re: springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final ( https://hibernate.atlassian.net/browse/HHH-15890?atlOrigin=eyJpIjoiNzgzNT... ) Hello, I have compiled locally and I can confirm that the issue is fixed in my minimal sample projects for DB2Dialect and DB2iDialect. Good job, thank you very much ! However, in my production project I run into this: java.lang.StackOverflowError: null at java.base/jdk.internal.misc.Unsafe.allocateUninitializedArray(Unsafe.java:1375) at java.base/java.lang.StringConcatHelper.newArray(StringConcatHelper.java:494) at java.base/java.lang.StringConcatHelper.newArrayWithSuffix(StringConcatHelper.java:475) at org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions(AbstractSqlAstTranslator.java:2943) at org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions(AbstractSqlAstTranslator.java:2911) at org.hibernate.dialect.DB2SqlAstTranslator.visitQuerySpec(DB2SqlAstTranslator.java:170) at org.hibernate.sql.ast.tree.select.QuerySpec.accept(QuerySpec.java:129) at org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions(AbstractSqlAstTranslator.java:2975) at org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions(AbstractSqlAstTranslator.java:2911) at org.hibernate.dialect.DB2SqlAstTranslator.visitQuerySpec(DB2SqlAstTranslator.java:170) at org.hibernate.sql.ast.tree.select.QuerySpec.accept(QuerySpec.java:129) at org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions(AbstractSqlAstTranslator.java:2975) at org.hibernate.sql.ast.spi.AbstractSqlAstTranslator.emulateFetchOffsetWithWindowFunctions(AbstractSqlAstTranslator.java:2911) at org.hibernate.dialect.DB2SqlAstTranslator.visitQuerySpec(DB2SqlAstTranslator.java:170) at org.hibernate.sql.ast.tree.select.QuerySpec.accept(QuerySpec.java:129) This seems related to the fix. Could this be a regression ? ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15890#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1932) Incomplete @Positive annotation's default message in fr

by Martine Deschênes (JIRA)

Martine Deschênes ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63bc5ff... ) *commented* on HV-1932 ( https://hibernate.atlassian.net/browse/HV-1932?atlOrigin=eyJpIjoiOWFkNTA1... ) Re: Incomplete @Positive annotation's default message in fr ( https://hibernate.atlassian.net/browse/HV-1932?atlOrigin=eyJpIjoiOWFkNTA1... ) https://github.com/hibernate/hibernate-validator/pull/1293 ( https://github.com/hibernate/hibernate-validator/pull/1293 ) ( https://hibernate.atlassian.net/browse/HV-1932#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1932#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1932) Incomplete @Positive annotation's default message in fr

by Martine Deschênes (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HV-1932) Incomplete @Positive annotation's default message in fr

by Martine Deschênes (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Dimitris Valasidis (JIRA)

Dimitris Valasidis ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6356848... ) *commented* on HHH-15984 ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiMWNkN2... ) Re: Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiMWNkN2... ) When i run the specific sql query on the database it runs well but when it runs from the application i got this error! ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16009) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field

by Andrey Lebedev (JIRA)

Andrey Lebedev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDgyZGQ4YzVl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMDgyZG... ) HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMDgyZG... ) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMDgyZG... ) Change By: Andrey Lebedev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Please, refer to this Repository that contains containing a project that reproduces the problem: [https://github.com/Andremoniy/hibernate-6-order-by-issue|https://github.c...] The error is: {noformat}o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 42122, SQLState: 42S22 o.h.engine.jdbc.spi.SqlExceptionHelper : Column "D1_0.DEPARTMENTCODE" not found; SQL statement: select c1_0.id,d1_0.company_id,d1_0.department_code,d1_0.name,c1_0.name from company c1_0 left join department d1_0 on c1_0.id=d1_0.company_id where c1_0.name=? order by d1_0.departmentCode desc [42122-214]{noformat} Basically, under certain conditions the column name provided in the {{OrderBy}} annotation is not transformed to the physical name of the column in the database. This is a combination of the three different conditions: # The field used in the {{OrderBy}} should be a part of a composite key on the mapped entity. In our case this is {{DepartmentId}} composite key: {noformat}public class DepartmentId implements Serializable { private Company company; private String departmentCode; }{noformat} 2. The field used in the {{OrderBy}} entity should contain more than a word in its name (if we rename {{departmentCode}} into {{code}}, the issue goes away). 3. There should be an HQL query that uses {{LEFT JOIN FETCH}} on the problematic entity. {noformat}@Query(""" SELECT c FROM Company c LEFT JOIN FETCH c.departments WHERE c.name = :name """ ) Optional<Company> findCompanyByName(@Param("name") String name);{noformat} ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15890) springboot 3.0.0 + hibernate 6.1.5.Final + IBM DB2 error after migrating from springboot 2.7.0 + hibernate 5.6.9.Final

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15984 ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiZWU3Nz... ) Re: Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiZWU3Nz... ) No idea what is wrong on your end, but according to the documentation ( https://www.postgresql.org/docs/9.6/sql-select.html#SQL-LIMIT ) , this syntax should also be supported on 9.6. In fact, I just tried running your query on 9.5 and it works for me. Maybe try updating your JDBC driver. Apart from that, note that 9.6 is not supported anymore and version 10 just recently EOLed. Starting with Hibernate 6.2 we make it clear by emitting a warning, that we only support a certain range of DB versions. In fact, we generally only support DB versions that are also still supported by the vendors. For 6.2 we will only support PostgreSQL 10+. If you can point us to a mistake that we made, we can look into that, but from what I see, it seems like your DB doesn’t behave well. Until then, I’ll close this ticket, but can reopen it if you can point me to something specific. ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16009) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field

by Andrey Lebedev (JIRA)

Andrey Lebedev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiM2Q4ZGNmMjU0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiM2Q4ZG... ) HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiM2Q4ZG... ) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiM2Q4ZG... ) Change By: Andrey Lebedev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Please, refer to this Repository that contains a project that reproduces the problem: [https://github.com/Andremoniy/hibernate-6-order-by-issue|https://github.c...] The error is: {noformat}o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 42122, SQLState: 42S22 o.h.engine.jdbc.spi.SqlExceptionHelper : Column "D1_0.DEPARTMENTCODE" not found; SQL statement: select c1_0.id,d1_0.company_id,d1_0.department_code,d1_0.name,c1_0.name from company c1_0 left join department d1_0 on c1_0.id=d1_0.company_id where c1_0.name=? order by d1_0.departmentCode desc [42122-214]{noformat} Basically, under certain conditions the column name provided in the {{OrderBy}} annotation is not transformed to the physical name of the column in the database. This is a combination of the three different conditions: # The field used in the {{OrderBy}} should be a part of a composite key on the mapped entity. In our case this is {{DepartmentId}} composite key: {noformat}public class DepartmentId implements Serializable { private Company company; private String departmentCode; }{noformat} # 2. The field used in the {{OrderBy}} entity should contain more than a word in its name (if we rename {{departmentCode}} into {{code}}, the issue goes away). # 3. There should be an HQL query that uses {{LEFT JOIN FETCH}} on the problematic entity. {noformat}@Query(""" SELECT c FROM Company c LEFT JOIN FETCH c.departments WHERE c.name = :name """ ) Optional<Company> findCompanyByName(@Param("name") String name);{noformat} ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16009) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field

by Andrey Lebedev (JIRA)

Andrey Lebedev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjJhN2E0OTdh... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMjJhN2... ) HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMjJhN2... ) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMjJhN2... ) Change By: Andrey Lebedev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Please, refer to this Repository that contains a project that reproduces the problem: [https://github.com/Andremoniy/hibernate-6-order-by-issue|https://github.c...] The error is: {noformat}o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 42122, SQLState: 42S22 o.h.engine.jdbc.spi.SqlExceptionHelper : Column "D1_0.DEPARTMENTCODE" not found; SQL statement: select c1_0.id,d1_0.company_id,d1_0.department_code,d1_0.name,c1_0.name from company c1_0 left join departme department d1_0 on c1_0.id=d1_0.company_id where c1_0.name=? order by d1_0.departmentCode desc [42122-214] {noformat} Basically, under certain conditions the column name provided in the {{OrderBy}} annotation is not transformed to the physical name of the column in the database. This is a combination of the three different conditions: # The field used in the {{OrderBy}} should be a part of a composite key on the mapped entity. In our case this is {{DepartmentId}} composite key: {noformat}public class DepartmentId implements Serializable { private Company company; private String departmentCode; }{noformat} # The field used in the {{OrderBy}} entity should contain more than a word in its name (if we rename {{departmentCode}} into {{code}}, the issue goes away). # There should be an HQL query that uses {{LEFT JOIN FETCH}} on the problematic entity. {noformat}@Query(""" SELECT c FROM Company c LEFT JOIN FETCH c.departments WHERE c.name = :name """ ) Optional<Company> findCompanyByName(@Param("name") String name);{noformat} ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16009) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field

by AndreyL (JIRA)

AndreyL ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMGZlZmRmYmNm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMGZlZm... ) HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMGZlZm... ) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiMGZlZm... ) Change By: AndreyL ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Please, refer to this Repository that contains a project that reproduces the problem: [https://github.com/Andremoniy/hibernate-6-order-by-issue|https://github.c...] The error is: {noformat}o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 42122, SQLState: 42S22 o.h.engine.jdbc.spi.SqlExceptionHelper : Column "D1_0.DEPARTMENTCODE" not found; SQL statement: select c1_0.id,d1_0.company_id,d1_0.department_code,d1_0.name,c1_0.name from company c1_0 left join departme{noformat} Basically, under certain conditions the column name provided in the {{OrderBy}} annotation is not transformed to the physical name of the column in the databse database. This is a combination of the three different conditions: # The field used in the {{OrderBy}} should be a part of a composite key on the mapped entity. In our case this is {{DepartmentId}} composite key: {noformat}public class DepartmentId implements Serializable { private Company company; private String departmentCode; }{noformat} # The field used in the {{OrderBy}} entity should contain more than a word in its name (if we rename {{departmentCode}} into {{code}}, the issue goes away). # There should be an HQL query that uses {{LEFT JOIN FETCH}} on the problematic entity. {noformat}@Query(""" SELECT c FROM Company c LEFT JOIN FETCH c.departments WHERE c.name = :name """ ) Optional<Company> findCompanyByName(@Param("name") String name);{noformat} ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16009) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field

by AndreyL (JIRA)

AndreyL ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiODFhZD... ) Re: jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiODFhZD... ) The error is: o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 42122, SQLState: 42S22 o.h.engine.jdbc.spi.SqlExceptionHelper : Column "D1_0.DEPARTMENTCODE" not found; SQL statement: select c1_0.id,d1_0.company_id,d1_0.department_code,d1_0.name,c1_0.name from company c1_0 left join departme ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16009) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field

by AndreyL (JIRA)

AndreyL ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNzYwZmFmN2Q5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiNzYwZm... ) HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiNzYwZm... ) jakarta @OrderBy annotation generates a non-transformed column name in the native query for a composite key's field ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiNzYwZm... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Created: 09/Jan/2023 09:38 AM Environment: Hibernate 6.1.6 Java 17 Priority: Blocker Reporter: AndreyL ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Please, refer to this Repository that contains a project that reproduces the problem: https://github.com/Andremoniy/hibernate-6-order-by-issue ( https://github.com/Andremoniy/hibernate-6-order-by-issue ) Basically, under certain conditions the column name provided in the OrderBy annotation is not transformed to the physical name of the column in the databse. This is a combination of the three different conditions: * The field used in the OrderBy should be a part of a composite key on the mapped entity. In our case this is DepartmentId composite key: public class DepartmentId implements Serializable { private Company company; private String departmentCode; } * The field used in the OrderBy entity should contain more than a word in its name (if we rename departmentCode into code , the issue goes away). * There should be an HQL query that uses LEFT JOIN FETCH on the problematic entity. @Query(""" SELECT c FROM Company c LEFT JOIN FETCH c.departments WHERE c.name = :name """ ) Optional<Company> findCompanyByName(@Param("name") String name); ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16009#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16003) Wrong alias used in subquery generated from JPQL

by Volker Seibt (JIRA)

Volker Seibt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a4ea7a... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzkzYmRiZWJm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16003?atlOrigin=eyJpIjoiYzkzYm... ) HHH-16003 ( https://hibernate.atlassian.net/browse/HHH-16003?atlOrigin=eyJpIjoiYzkzYm... ) Wrong alias used in subquery generated from JPQL ( https://hibernate.atlassian.net/browse/HHH-16003?atlOrigin=eyJpIjoiYzkzYm... ) Change By: Volker Seibt ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a4ea7a... ) For this JPQL {code:java}select mdf.id from MasterDataFileEntity mdf where mdf.dataImportStatus = 'SUCCESS' and mdf.metaData.country = :countryCode and mdf.metaData.transportMode = :transportMode and mdf.metaData.product = :product and mdf.importFinishedAt = (select max(mdf.importFinishedAt) from MasterDataFileEntity mdf where mdf.dataImportStatus = 'SUCCESS' and mdf.metaData.country = :countryCode and mdf.metaData.transportMode = :transportMode and mdf.metaData.product = :product){code} Hibernate generates this SQL {code:sql}select m1_0.id from PEL.pel_master_data_file m1_0 where m1_0.data_import_status='SUCCESS' and m1_0.country_code=? and m1_0.transport_mode=? and m1_0.product=? and m1_0.import_finished_at= (select max(m2_0.import_finished_at) from PEL.pel_master_data_file m2_0 where m2_0.data_import_status='SUCCESS' and m1_0.country_code=? and m1_0.transport_mode=? and m1_0.product=?){code} The table alias for the subquery for all conditions joined by {{and}} is wrong, taken not from the subquery but from the main query. Workaround is to use a different alias for the subquery in JPQL. Test case: [https://github.com/vseibt/hibernate-test-case-templates/commit/405bc954f7...] ( https://hibernate.atlassian.net/browse/HHH-16003#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16003#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Dimitris Valasidis (JIRA)

Dimitris Valasidis ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6356848... ) *commented* on HHH-15984 ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiN2FkYj... ) Re: Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiN2FkYj... ) PostgreSQL 9.6.2 on x86_64-pc-linux-gnu ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15984 ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiYTFjMD... ) Re: Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiYTFjMD... ) What is the version of the database that you are using? ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15984) Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error

by Dimitris Valasidis (JIRA)

Dimitris Valasidis ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6356848... ) *commented* on HHH-15984 ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiMTA4Zj... ) Re: Pagination error with Postgres : SQL Error: 0, SQLState: 42601 ERROR: syntax error ( https://hibernate.atlassian.net/browse/HHH-15984?atlOrigin=eyJpIjoiMTA4Zj... ) I have used : * org.hibernate.dialect.PostgreSQL94Dialect * org.hibernate.dialect.PostgreSQLDialect * org.hibernate.dialect.PostgreSQL95Dialect and i havent seen any changes. ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15984#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15983) PostgreSQLDialect db version detection failure blocks deployment

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15983) PostgreSQLDialect db version detection failure blocks deployment

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15983 ( https://hibernate.atlassian.net/browse/HHH-15983?atlOrigin=eyJpIjoiNTUyYz... ) Re: PostgreSQLDialect db version detection failure blocks deployment ( https://hibernate.atlassian.net/browse/HHH-15983?atlOrigin=eyJpIjoiNTUyYz... ) I don’t think that it is just the dialect that will attempt to connect to the database. There are other metadata that are extracted through JDBC, so if you want to make sure that no JDBC connection is established, you will have to use the config setting that I suggested. Since there is no way to query JDBC driver information without a connection, there are quite a few optimizations that you might possibly be missing out on though, so maybe consider some sort of build where you have a test instance available or don’t trigger this eager deployment and instead deploy that container to a staging environment for catching startup errors. ( https://hibernate.atlassian.net/browse/HHH-15983#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15983#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16003) Wrong alias used in subquery generated from JPQL

by Volker Seibt (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16007) PropertyAccessException when deleting entities with Embeddables with child collections

by Christoph Watzl (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16008) add StatelessSession.joinTransaction()

by Gavin King (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16008) add StatelessSession.joinTransaction()

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16008 ( https://hibernate.atlassian.net/browse/HHH-16008?atlOrigin=eyJpIjoiMzkyY2... ) Re: add StatelessSession.joinTransaction() ( https://hibernate.atlassian.net/browse/HHH-16008?atlOrigin=eyJpIjoiMzkyY2... ) Done. ( https://hibernate.atlassian.net/browse/HHH-16008#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16008#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16008) add StatelessSession.joinTransaction()

by Gavin King (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15982) Bidirectional one-to-one associations produce child entities with null parent entity references

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-15950) AssertionError with bidirectional OneToOne relation using AttributeConverter for the FK

by Christian Beikov (JIRA)

2 years, 12 months

1
0
0 / 0

[JIRA] (HHH-16007) PropertyAccessException when deleting enties with Embeddables with child collections

by Christoph Watzl (JIRA)

Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmE1N2UwNDRl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiMmE1N2... ) HHH-16007 ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiMmE1N2... ) PropertyAccessException when deleting enties with Embeddables with child collections ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiMmE1N2... ) Change By: Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We are currently trying to upgrade a project from Hibernate 5 to 6, which When using an {{@Embedded}} value object that has a collection with orphan removal, trying to delete the root entity throws a {{PropertyAccessException}}. The same scenario used to work without issue in Hibernate 5. I have prepared a [minimal example project to reproduce|]. Model: {code:java}@Entity public class Parent { @Id private final String id; @Embedded private final Child child; // ... ctors & accessors ... } @Embeddable public class Child { @OneToMany(cascade = CascadeType.ALL, orphanRemoval = true) private final List<Grandchild> grandchildren = new ArrayList<>(); // ... ctors & accessors ... } @Entity public class Grandchild { @Id private final String id; // .. ctors & accessors ... }{code} Test case: {code:java}var parent = new Parent("123", new Child(List.of(new Grandchild("xyz")))); entityManager.persist(parent); entityManager.flush(); entityManager.clear(); entityManager.remove(entityManager.getReference(Parent.class, "123")); entityManager.flush(); // throws PersistenceException{code} This will throw: *Exception thrown* {noformat}jakarta.persistence.PersistenceException: Converting `org.hibernate.property.access.spi.PropertyAccessException` to JPA `PersistenceException` : Error accessing field [private final java.lang.String org.hibernate.bugs.model.Parent.id] by reflection for persistent property [org.hibernate.bugs.model.Parent#id] : org.hibernate.bugs.model.Child@77c66a4f at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:165) at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:175) at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:182) at org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1429) at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1411) at org.hibernate.bugs.JPAUnitTestCase.hhh123Test(JPAUnitTestCase.java:47) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69) at com.intellij.rt.junit.IdeaTestRunner$Repeater$1.execute(IdeaTestRunner.java:38) at com.intellij.rt.execution.junit.TestsRepeater.repeat(TestsRepeater.java:11) at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:35) at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:235) at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:54) Caused by: org.hibernate.property.access.spi.PropertyAccessException: Error accessing field [private final java.lang.String org.hibernate.bugs.model.Parent.id] by reflection for persistent property [org.hibernate.bugs.model.Parent#id] : org.hibernate.bugs.model.Child@77c66a4f at org.hibernate.property.access.spi.GetterFieldImpl.get(GetterFieldImpl.java:48) at org.hibernate.metamodel.mapping.internal.BasicEntityIdentifierMappingImpl.getIdentifier(BasicEntityIdentifierMappingImpl.java:147) at org.hibernate.persister.entity.AbstractEntityPersister.getIdentifier(AbstractEntityPersister.java:5254) at org.hibernate.engine.internal.Collections.processDereferencedCollection(Collections.java:70) at org.hibernate.engine.internal.Collections.processUnreachableCollection(Collections.java:49) at org.hibernate.event.internal.AbstractFlushingEventListener.lambda$flushCollections$1(AbstractFlushingEventListener.java:236) at org.hibernate.engine.internal.StatefulPersistenceContext.forEachCollectionEntry(StatefulPersistenceContext.java:1127) at org.hibernate.event.internal.AbstractFlushingEventListener.flushCollections(AbstractFlushingEventListener.java:233) at org.hibernate.event.internal.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:91) at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:38) at org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:107) at org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1425) ... 31 more Caused by: java.lang.IllegalArgumentException: Can not set final java.lang.String field org.hibernate.bugs.model.Parent.id to org.hibernate.bugs.model.Child at java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167) at java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171) at java.base/jdk.internal.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:58) at java.base/jdk.internal.reflect.UnsafeQualifiedObjectFieldAccessorImpl.get(UnsafeQualifiedObjectFieldAccessorImpl.java:38) at java.base/java.lang.reflect.Field.get(Field.java:425) at org.hibernate.property.access.spi.GetterFieldImpl.get(GetterFieldImpl.java:44) ... 42 more{noformat} Of particular interest is this message: {noformat}Can not set final java.lang.String field org.hibernate.bugs.model.Parent.id to org.hibernate.bugs.model.Child{noformat} Apparently, for some reason, {{AbstractEntityPersister}} is trying to reflectively access the id property of the Parent entity but applies the getter to the embeddable child value type, which makes no sense. ( https://hibernate.atlassian.net/browse/HHH-16007#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16007#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100213- sha1:1fa7b87 )

2 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2023