January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16062) jakarta.persistence.query.timeout not working on Hibernate 6.1.6

by Phillip Webb (JIRA)

Phillip Webb ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16062 ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiM2IxOG... ) Re: jakarta.persistence.query.timeout not working on Hibernate 6.1.6 ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiM2IxOG... ) I’ve recreated the issue without any Spring involved. You can find the repo at https://github.com/philwebb/HHH-16062 ( https://github.com/philwebb/HHH-16062 ) The problem doesn’t happen when using createQuery("") , but it does when using createQuery(criteriaQuery). ( https://hibernate.atlassian.net/browse/HHH-16062#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16062#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16070) Exception when find by association id that is a generic @EmbeddedId with @MappedSuperclass

by Francisco Sousa (JIRA)

Francisco Sousa ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e949f3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNmYyMjk2Njgx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16070?atlOrigin=eyJpIjoiNmYyMj... ) HHH-16070 ( https://hibernate.atlassian.net/browse/HHH-16070?atlOrigin=eyJpIjoiNmYyMj... ) Exception when find by association id that is a generic @EmbeddedId with @MappedSuperclass ( https://hibernate.atlassian.net/browse/HHH-16070?atlOrigin=eyJpIjoiNmYyMj... ) Issue Type: Bug Affects Versions: 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6 Assignee: Unassigned Created: 19/Jan/2023 15:35 PM Priority: Major Reporter: Francisco Sousa ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5e949f3... ) I have the following abstracts base classes: @MappedSuperclass public abstract class DomainEntityId implements Serializable { private final Long value; protected DomainEntityId() { this.value = RandomGenerator.getDefault().nextLong(); } public Long getValue() { return value; } } @MappedSuperclass public abstract class DomainEntityModel<ID extends DomainEntityId> { @EmbeddedId @AttributeOverride(name = "value" , column = @Column(name = "id" )) private final ID id; protected DomainEntityModel(ID id) { this.id = id; } @NonNull public ID getId() { return id; } } and the following concrete entities: @Embeddable public class CustomerId extends DomainEntityId {} @Entity public class Customer extends DomainEntityModel<CustomerId> { private Integer code; private String name; public Customer() { super(new CustomerId()); } public Integer getCode() { return code; } public void setCode(Integer code) { this.code = code; } public String getName() { return name; } public void setName(String name) { this.name = name; } } @Embeddable public class InvoiceId extends DomainEntityId {} @Entity public class Invoice extends DomainEntityModel<InvoiceId> { private Integer number; @ManyToOne private Customer customer; public Invoice() { super(new InvoiceId()); } public Integer getNumber() { return number; } public void setNumber(Integer number) { this.number = number; } public Customer getCustomer() { return customer; } public void setCustomer(Customer customer) { this.customer = customer; } } When I try to find invoices by customer id, I get the following exception: java.lang.IllegalArgumentException: Argument [br.com.leverinfo.mappedsuperclassissue.model.CustomerId@3c2c9b59] of type [br.com.leverinfo.mappedsuperclassissue.model.CustomerId] did not match parameter type [br.com.leverinfo.mappedsuperclassissue.model.InvoiceId (n/a)] at org.hibernate.query.spi.QueryParameterBindingValidator.validate(QueryParameterBindingValidator.java:84) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.spi.QueryParameterBindingValidator.validate(QueryParameterBindingValidator.java:31) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.internal.QueryParameterBindingImpl.validate(QueryParameterBindingImpl.java:339) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.internal.QueryParameterBindingImpl.setBindValue(QueryParameterBindingImpl.java:129) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.spi.AbstractCommonQueryContract.setParameter(AbstractCommonQueryContract.java:1066) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.spi.AbstractSelectionQuery.setParameter(AbstractSelectionQuery.java:774) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.sqm.internal.QuerySqmImpl.setParameter(QuerySqmImpl.java:1329) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.hibernate.query.sqm.internal.QuerySqmImpl.setParameter(QuerySqmImpl.java:131) ~[hibernate-core-6.1.6.Final.jar:6.1.6.Final] at org.springframework.data.jpa.repository.query.QueryParameterSetter$BindableQuery.setParameter(QueryParameterSetter.java:314) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.QueryParameterSetter$NamedOrIndexedQueryParameterSetter.lambda$setParameter$3(QueryParameterSetter.java:111) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.QueryParameterSetter$ErrorHandling$1.execute(QueryParameterSetter.java:136) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.QueryParameterSetter$NamedOrIndexedQueryParameterSetter.setParameter(QueryParameterSetter.java:111) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.ParameterBinder.bind(ParameterBinder.java:83) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.ParameterBinder.bind(ParameterBinder.java:75) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.ParameterBinder.bindAndPrepare(ParameterBinder.java:97) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.PartTreeJpaQuery$QueryPreparer.invokeBinding(PartTreeJpaQuery.java:312) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.PartTreeJpaQuery$QueryPreparer.createQuery(PartTreeJpaQuery.java:231) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.PartTreeJpaQuery.doCreateQuery(PartTreeJpaQuery.java:102) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.AbstractJpaQuery.createQuery(AbstractJpaQuery.java:234) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.JpaQueryExecution$CollectionExecution.doExecute(JpaQueryExecution.java:127) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.JpaQueryExecution.execute(JpaQueryExecution.java:90) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.AbstractJpaQuery.doExecute(AbstractJpaQuery.java:148) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.jpa.repository.query.AbstractJpaQuery.execute(AbstractJpaQuery.java:136) ~[spring-data-jpa-3.0.0.jar:3.0.0] at org.springframework.data.repository.core.support.RepositoryMethodInvoker.doInvoke(RepositoryMethodInvoker.java:136) ~[spring-data-commons-3.0.0.jar:3.0.0] at org.springframework.data.repository.core.support.RepositoryMethodInvoker.invoke(RepositoryMethodInvoker.java:120) ~[spring-data-commons-3.0.0.jar:3.0.0] at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.doInvoke(QueryExecutorMethodInterceptor.java:164) ~[spring-data-commons-3.0.0.jar:3.0.0] at org.springframework.data.repository.core.support.QueryExecutorMethodInterceptor.invoke(QueryExecutorMethodInterceptor.java:143) ~[spring-data-commons-3.0.0.jar:3.0.0] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[spring-aop-6.0.3.jar:6.0.3] at org.springframework.data.projection.DefaultMethodInvokingMethodInterceptor.invoke(DefaultMethodInvokingMethodInterceptor.java:77) ~[spring-data-commons-3.0.0.jar:3.0.0] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[spring-aop-6.0.3.jar:6.0.3] at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123) ~[spring-tx-6.0.3.jar:6.0.3] at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388) ~[spring-tx-6.0.3.jar:6.0.3] at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119) ~[spring-tx-6.0.3.jar:6.0.3] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[spring-aop-6.0.3.jar:6.0.3] at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:137) ~[spring-tx-6.0.3.jar:6.0.3] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:184) ~[spring-aop-6.0.3.jar:6.0.3] at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor$CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:134) ~[spring-data-jpa-3.0.0.jar:3.0.0] ... I’ve debug as I could and AFAICS, as both concrete entities share the same superclass, there is only one MappedSuperclass ( https://docs.jboss.org/hibernate/orm/6.1/javadocs/org/hibernate/mapping/M... ) instance and the DeclaredIdentifierProperty is being replaced with the id of the last entity. After, this id is used to validate the query parameter value and they are incompatibles. There is a similar problem https://hibernate.atlassian.net/browse/HHH-11955 ( https://hibernate.atlassian.net/browse/HHH-11955 ) , although I’m not sure that is exactly the same. In this repository https://github.com/franciscosousabr/mappedsuperclassissue ( https://github.com/franciscosousabr/mappedsuperclassissue ) I have an example of this issue. In branch master the error is occurring. In branch hibernate-5 , the same code works well. ( https://hibernate.atlassian.net/browse/HHH-16070#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16070#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16068) Named native queries when retrieved from the entity manager lose ordinal parameter mapping

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

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

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=eyJpIjoiMDhiY2U2NmU0... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16006?atlOrigin=eyJpIjoiMDhiY2... ) HHH-16006 ( https://hibernate.atlassian.net/browse/HHH-16006?atlOrigin=eyJpIjoiMDhiY2... ) Implement an "additional mapping" contributor SPI ( https://hibernate.atlassian.net/browse/HHH-16006?atlOrigin=eyJpIjoiMDhiY2... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Implement an "additional mapping" contributor SPI. Basically what {{AdditionalJaxbMappingProducer}} is today, but allowing additional mechanisms of contribution. {code:java}interface AdditionalMappingContributor { void contributeMappings( AdditionalMappingContributions contributions, InFlightMetadataCollector metadata, ResourceStreamLocator resourceStreamLocator, MetadataBuildingContext buildingContext); } interface MappingContributions AdditionalMappingContributions { void contributeEntity(Class<?> entityType); void contributeBinding(InputStream xmlStream); void contributeBinding(JaxbEntityMappings mappingJaxbBinding); void contributeBinding(JaxbHbmHibernateMapping hbmJaxbBinding); void contributeTable(Table table); void contributeSequence(Sequence sequence); void contributeAuxiliaryDatabaseObject(AuxiliaryDatabaseObject auxiliaryDatabaseObject); }{code} Ultimately will support contributing {{org.hibernate.mapping.PersistentClass}} references as well, though the exact semantics of that need to be worked out. E.g. what all gets auto-handled? Table? Secondary tables? etc ( https://hibernate.atlassian.net/browse/HHH-16006#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16006#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

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

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=eyJpIjoiM2Q1MTBlYWMy... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16006?atlOrigin=eyJpIjoiM2Q1MT... ) HHH-16006 ( https://hibernate.atlassian.net/browse/HHH-16006?atlOrigin=eyJpIjoiM2Q1MT... ) Implement an "additional mapping" contributor SPI ( https://hibernate.atlassian.net/browse/HHH-16006?atlOrigin=eyJpIjoiM2Q1MT... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Implement an "additional mapping" contributor SPI. Basically what {{AdditionalJaxbMappingProducer}} is today, but allowing additional mechanisms of contribution - e. g. direct {{PersistentClass}}, {{Table}}, etc. references from {{org.hibernate.mapping}} Initial proposal - { noformat code:java }interface AdditionalMappingContributor { void contributeMappings( MappingContributions AdditionalMappingContributions contributions, IndexView jandexIndex InFlightMetadataCollector metadata , MappingBinder jaxbBinder ResourceStreamLocator resourceStreamLocator , MetadataBuildingContext buildingContext); } interface MappingContributions { void contribute contributeEntity ( Binding Class <?> jaxbBinding entityType ); void contribute contributeBinding ( PersistentClass entity InputStream xmlStream ); voide contribute void contributeBinding ( JaxbEntityMappings mappingJaxbBinding); void contributeBinding(JaxbHbmHibernateMapping hbmJaxbBinding); void contributeTable( Table table); void contributeSequence(Sequence sequence); void contributeAuxiliaryDatabaseObject(AuxiliaryDatabaseObject auxiliaryDatabaseObject); }{code} Ultimately will support contributing {{org. hibernate. mapping. PersistentClass } {noformat } references as well, though the exact semantics of that need to be worked out. E.g. what all gets auto-handled? Table? Secondary tables? etc ( https://hibernate.atlassian.net/browse/HHH-16006#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16006#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16069) Defer handling of custom types until after deployment time

by Scott Marlow (JIRA)

Scott Marlow ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzg1YzAwZGUx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16069?atlOrigin=eyJpIjoiMzg1Yz... ) HHH-16069 ( https://hibernate.atlassian.net/browse/HHH-16069?atlOrigin=eyJpIjoiMzg1Yz... ) Defer handling of custom types until after deployment time ( https://hibernate.atlassian.net/browse/HHH-16069?atlOrigin=eyJpIjoiMzg1Yz... ) Issue Type: Bug Affects Versions: 6.1.5 Assignee: Unassigned Components: hibernate-core Created: 19/Jan/2023 14:24 PM Fix Versions: 6.2.0 Priority: Major Reporter: Scott Marlow ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) https://groups.google.com/d/msgid/wildfly/ba3a578f-7f42-4fda-8736-9fb95c9... ( https://groups.google.com/d/msgid/wildfly/ba3a578f-7f42-4fda-8736-9fb95c9... ) reported exception “org.hibernate.resource.beans.container.internal.NotYetReadyException: CDI BeanManager not (yet) ready to use" being thrown during the second 2-phase bootstrap deployment which is too early. Please defer the org.hibernate.mapping.BasicValue.setExplicitCustomType() processing until later. Paste of the exception from the above linked user report: “ 7:08:49,386 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 80) MSC000001: Failed to start service jboss.persistenceunit."XXX": org.jboss.msc.service.StartException in service jboss.persistenceunit.""XXX": org.hibernate.resource.beans.container.internal.NotYetReadyException: CDI BeanManager not (yet) ready to use at org.jbos...@27.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199) at org.jbos...@27.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129) at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) at org.wildfly.secu...@2.0.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664) at org.jbos...@27.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214) at org.jbos...@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jbos...@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Thread.java:833) at org.jbos...@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: org.hibernate.resource.beans.container.internal.NotYetReadyException: CDI BeanManager not (yet) ready to use at org.hi...@6.1.5.Final//org.hibernate.resource.beans.container.internal.JpaCompliantLifecycleStrategy$NamedBeanImpl.initialize(JpaCompliantLifecycleStrategy.java:231) at org.hi...@6.1.5.Final//org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl$NamedBeanImpl.initialize(CdiBeanContainerExtendedAccessImpl.java:165) at org.hi...@6.1.5.Final//org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl$NamedBeanImpl.getBeanInstance(CdiBeanContainerExtendedAccessImpl.java:172) at org.hi...@6.1.5.Final//org.hibernate.resource.beans.internal.ManagedBeanRegistryImpl$ContainedBeanManagedBeanAdapter.getBeanInstance(ManagedBeanRegistryImpl.java:155) at org.hi...@6.1.5.Final//org.hibernate.mapping.BasicValue.setExplicitCustomType(BasicValue.java:828) at org.hi...@6.1.5.Final//org.hibernate.cfg.annotations.BasicValueBinder.fillSimpleValue(BasicValueBinder.java:1238) at org.hi...@6.1.5.Final//org.hibernate.cfg.SetBasicValueTypeSecondPass.doSecondPass(SetBasicValueTypeSecondPass.java:26) at org.hi...@6.1.5.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.processSecondPasses(InFlightMetadataCollectorImpl.java:1782) at org.hi...@6.1.5.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.processSecondPasses(InFlightMetadataCollectorImpl.java:1729) at org.hi...@6.1.5.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:300) at org.hi...@6.1.5.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1350) at org.hi...@6.1.5.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1421) at org.hibernate.ji...@27.0.1.Final//org.jboss.as.jpa.hibernate.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:45) at org.jbos...@27.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171) ... 10 more Caused by: java.lang.NullPointerException: Cannot invoke "jakarta.enterprise.inject.spi.BeanManager.createCreationalContext(jakarta.enterprise.context.spi.Contextual)" because "this.beanManager" is null at org.hi...@6.1.5.Final//org.hibernate.resource.beans.container.internal.JpaCompliantLifecycleStrategy$NamedBeanImpl.initialize(JpaCompliantLifecycleStrategy.java:228) ” ( https://hibernate.atlassian.net/browse/HHH-16069#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16069#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16041) Unable to set scale (# of digits to right of decimal place) of stored procedure NUMERIC / DECIMAL output types

by James Johnson (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16041) Unable to set scale (# of digits to right of decimal place) of stored procedure NUMERIC / DECIMAL output types

by James Johnson (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4782) Retrieve decimal scale automatically from entity identifiers

by Automation for Jira (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16068) Named native queries when retrieved from the entity manager lose ordinal parameter mapping

by Björn Kautler (JIRA)

Björn Kautler ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTFmODdjMzU0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16068?atlOrigin=eyJpIjoiOTFmOD... ) HHH-16068 ( https://hibernate.atlassian.net/browse/HHH-16068?atlOrigin=eyJpIjoiOTFmOD... ) Named native queries when retrieved from the entity manager lose ordinal parameter mapping ( https://hibernate.atlassian.net/browse/HHH-16068?atlOrigin=eyJpIjoiOTFmOD... ) Issue Type: Bug Affects Versions: 6.1.5 Assignee: Unassigned Attachments: hibernate-problem.zip Created: 19/Jan/2023 08:18 AM Priority: Major Reporter: Björn Kautler ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) It seems that if you have a native query where an ordinal parameter is used multiple times, then the query is added and then retrieved by name, Hibernate breaks. It seems like it internally changed all parameters to ? but then forgot the mapping from ordinal parameter to query parameter. See the tests in the attached reproducer project. ( https://hibernate.atlassian.net/browse/HHH-16068#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16068#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16049) Setting a property to its current value with bytecode enhancement enabled results in unnecessary SQL Update in some (many) cases

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16067) Upgrade to Jackson 2.14.1

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16066) Upgrade Jandex to 3.0.5

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16065) Upgrade Jakarta CDI API to 4.0.0

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16064) Upgrade JBoss Logging to 3.5.0.Final

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16063) Upgrade Micrometer to 1.10.3

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16061) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16060) Upgrade Narayana used for integration testing to version 6.0.0.CR1

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16062) jakarta.persistence.query.timeout not working on Hibernate 6.1.6

by Thiago Rodrigues Coelho (JIRA)

Thiago Rodrigues Coelho ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c94ca... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjM2YmJmNDY0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiNjM2Ym... ) HHH-16062 ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiNjM2Ym... ) jakarta.persistence.query.timeout not working on Hibernate 6.1.6 ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiNjM2Ym... ) Change By: Thiago Rodrigues Coelho ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c94ca... ) I have opened a GitHub ticket to Spring team as a result to investigate a propertie that controls query timeout ([Spring Data query timeout · Issue #33866 · spring-projects/spring-boot (github.com)|https://github.com/spring-projects/spring-boot/issues/33866]). After update to Hibernate 6 version propertie *jakarta.persistence.query.timeout* seems not work anymore. On previous version (Hibernate 5.6.14) propertie *javax.persistence.query.timeout* is successfully set and work as expected. Looks like when {noformat}org.hibernate.query.sqm.internal.QuerySqmImpl{noformat} is created it has its own {noformat}org.hibernate.query.internal.QueryOptionsImpl{noformat} and method {noformat}setTimeout{noformat} is never called on that instance. I have attached some debug screenshots (using Hibernate 6.1.6 version). Propertie being set on {noformat}org.hibernate.query.spi.AbstractCommonQueryContract{noformat} !image-20230119-140915.png|width=1088,height=457! !image-20230119-141028.png|width=1151,height=465! Then propertie is successfully set on : {noformat}org.hibernate.query.sqm.internal.QuerySqmImpl{noformat} !image-20230119-141043.png|width=455,height=431! Method {noformat}org.hibernate.query.sqm.internal.QuerySqmImpl.getTimeout(){noformat} returns null: !image-20230119-141142.png|width=408,height=411! MySQL database is being used, by the way. Is there any additional configuration that must be set? Couldn’t find anything on Hibernate documentation regarding it. Let me know if you have any question. Thanks in advance. ( https://hibernate.atlassian.net/browse/HHH-16062#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16062#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16062) jakarta.persistence.query.timeout not working on Hibernate 6.1.6

by Thiago Rodrigues Coelho (JIRA)

Thiago Rodrigues Coelho ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c94ca... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDdmYzlkNTYx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiMDdmYz... ) HHH-16062 ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiMDdmYz... ) jakarta.persistence.query.timeout not working on Hibernate 6.1.6 ( https://hibernate.atlassian.net/browse/HHH-16062?atlOrigin=eyJpIjoiMDdmYz... ) Issue Type: Bug Assignee: Unassigned Attachments: image-20230119-140915.png, image-20230119-141028.png, image-20230119-141043.png, image-20230119-141142.png Created: 19/Jan/2023 06:13 AM Priority: Critical Reporter: Thiago Rodrigues Coelho ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c94ca... ) I have opened a GitHub ticket to Spring team as a result to investigate a propertie that controls query timeout ( Spring Data query timeout · Issue #33866 · spring-projects/spring-boot (github.com) ( https://github.com/spring-projects/spring-boot/issues/33866 ) ). After update to Hibernate 6 version propertie *jakarta.persistence.query.timeout* seems not work anymore. On previous version (Hibernate 5.6.14) propertie *javax.persistence.query.timeout* is successfully set and work as expected. Looks like when org.hibernate.query.sqm.internal.QuerySqmImpl is created it has its own org.hibernate.query.internal.QueryOptionsImpl and method setTimeout is never called on that instance. I have attached some debug screenshots (using Hibernate 6.1.6 version). Propertie being set on org.hibernate.query.spi.AbstractCommonQueryContract Then propertie is successfully set on : org.hibernate.query.sqm.internal.QuerySqmImpl Method org.hibernate.query.sqm.internal.QuerySqmImpl.getTimeout() returns null: Is there any additional configuration that must be set? Couldn’t find anything on Hibernate documentation regarding it. Let me know if you have any question. Thanks in advance. ( https://hibernate.atlassian.net/browse/HHH-16062#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16062#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16061) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity

by Alexander Schwartz (JIRA)

Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmVmM2YxZmNm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiYmVmM2... ) HHH-16061 ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiYmVmM2... ) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiYmVmM2... ) Change By: Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) I'm working on upgrading Keycloak from H5 to H6. I see the following warning: {quote}SqmDynamicInstantiation:174 WARN Argument [org.hibernate.bugs.cl.Parent as p] for dynamic Map instantiation did not declare an 'injection alias' [parent] but such aliases are needed for dynamic Map instantiations; will likely cause problems later translating sqm{quote} This is the query, please note that we put the entity in the map. {quote}select new map(p as parent) from parent p{quote} This example is simple and looks stupid with a single map entry - in the real code we place other fields from joins in it as well. Still, it is a minimal reproducer. Despite the warning it seems to work fine. Here's some extracted sample code: [https://github.com/hibernate/hibernate-test-case-templates/compare/main.....] How can I get rid of the warning? Although I don’t see an immediate impact, am I missing something here it that might have an impact? Zulip discussion: [https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user/topi...] This is tracked by the Keycloak team in issue: [https://github.com/keycloak/keycloak/issues/16507|https://github.com/keyc...] ( https://hibernate.atlassian.net/browse/HHH-16061#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16061#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16061) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity

by Alexander Schwartz (JIRA)

Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTQ0ZTlmNDc3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiOTQ0ZT... ) HHH-16061 ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiOTQ0ZT... ) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiOTQ0ZT... ) Change By: Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) I'm working on upgrading Keycloak from H5 to H6. I see the following warning: {quote}SqmDynamicInstantiation:174 WARN Argument [org.hibernate.bugs.cl.Parent as p] for dynamic Map instantiation did not declare an 'injection alias' [parent] but such aliases are needed for dynamic Map instantiations; will likely cause problems later translating sqm{quote} This is the query, please note that we put the entity in the map. {quote}select new map(p as parent) from parent p{quote} This example is simple and looks stupid with a single map entry - in the real code we place other fields from joins in it as well. Still, it is a minimal reproducer. Despite the warning it seems to work fine. Here's some extracted sample code: [https://github.com/hibernate/hibernate-test-case-templates/compare/main.....] How can I get rid of the warning? Although I don’t see an immediate impact, am I missing something here it might have an impact? Zulip discussion: [https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user/topi...] This is tracked by the Keycloak team in issue: [https://github.com/keycloak/keycloak/issues/16507|https://github.com/keyc...] ( https://hibernate.atlassian.net/browse/HHH-16061#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16061#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16061) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity

by Alexander Schwartz (JIRA)

Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNmI2YWYyMDA5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiNmI2YW... ) HHH-16061 ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiNmI2YW... ) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiNmI2YW... ) Change By: Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) I'm working on upgrading Keycloak from H5 to H6. I see the following warning: {quote}SqmDynamicInstantiation:174 WARN Argument [org.hibernate.bugs.cl.Parent as p] for dynamic Map instantiation did not declare an 'injection alias' [parent] but such aliases are needed for dynamic Map instantiations; will likely cause problems later translating sqm{quote} This is the query, please note that we put the entity in the map. {quote}select new map(p as parent) from parent p{quote} This example is simple and looks stupid with a single map entry - in the real code we place other fields from joins in it as well. Still, it is a minimal reproducer. Despite the warning it seems to work fine. Here's some extracted sample code: [https://github.com/hibernate/hibernate-test-case-templates/compare/main.....] How can I get rid of the warning? Although I don’t see an immediate impact, am I missing something here it might have an impact? Zulip discussion: [https://hibernate.zulipchat.com/#narrow/stream/132096-hibernate-user/topi...] ( https://hibernate.atlassian.net/browse/HHH-16061#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16061#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16061) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity

by Alexander Schwartz (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16061) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity

by Alexander Schwartz (JIRA)

Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODhiNWNmNTlj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiODhiNW... ) HHH-16061 ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiODhiNW... ) SqmDynamicInstantiation warns about dynamic Map instantiation when using an entity ( https://hibernate.atlassian.net/browse/HHH-16061?atlOrigin=eyJpIjoiODhiNW... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Created: 19/Jan/2023 05:18 AM Priority: Major Reporter: Alexander Schwartz ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6267ec4... ) I'm working on upgrading Keycloak from H5 to H6. I see the following warning: > > > > SqmDynamicInstantiation:174 WARN Argument [org.hibernate.bugs.cl.Parent as > p] for dynamic Map instantiation did not declare an 'injection alias' [parent] > but such aliases are needed for dynamic Map instantiations; will likely > cause problems later translating sqm > > This is the query, please note that we put the entity in the map. > > > > select new map(p as parent) from parent p > > This example is simple and looks stupid with a single map entry - in the real code we place other fields from joins in it as well. Still, it is a minimal reproducer. Despite the warning it seems to work fine. Here's some extracted sample code: https://github.com/hibernate/hibernate-test-case-templates/compare/main..... ( https://github.com/hibernate/hibernate-test-case-templates/compare/main..... ) How can I get rid of the warning? Although I don’t see an immediate impact, am I missing something here it might have an impact? ( https://hibernate.atlassian.net/browse/HHH-16061#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16061#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16043) Hibernate 6.x brakes collection batch fetching

by Marco Belladelli (JIRA)

2 years, 11 months

1
0
0 / 0

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

by Christoph Watzl (JIRA)

Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16007 ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiYTJiNz... ) Re: PropertyAccessException when deleting entities with Embeddables with child collections ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiYTJiNz... ) Also not reproducible the current head of the 6.1 maintenance branch. I guess we’ll just have to wait for 6.1.7 then. ( 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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15921) @BatchSize and @IdClass on join column throws exception

by Daniel Freudenberger (JIRA)

Daniel Freudenberger ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWYyZDFlZDVi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15921?atlOrigin=eyJpIjoiZWYyZD... ) HHH-15921 ( https://hibernate.atlassian.net/browse/HHH-15921?atlOrigin=eyJpIjoiZWYyZD... ) @BatchSize and @IdClass on join column throws exception ( https://hibernate.atlassian.net/browse/HHH-15921?atlOrigin=eyJpIjoiZWYyZD... ) Change By: Daniel Freudenberger ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The combination of @BatchSize on the parent entity and @Idclass on the child entity makes hibernate fail with the following error. {noformat}org.hibernate.HibernateException: Unable to resolve property: {id}{noformat} Maybe the mapping should be different, but it worked fine before updating to Hibernate 6+. Please see the attached the case for details. ( https://hibernate.atlassian.net/browse/HHH-15921#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15921#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16060) Upgrade Narayana used for integration testing to version 6.0.0.CR1

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTIzZWMyOGZk... ) / Task ( https://hibernate.atlassian.net/browse/HHH-16060?atlOrigin=eyJpIjoiNTIzZW... ) HHH-16060 ( https://hibernate.atlassian.net/browse/HHH-16060?atlOrigin=eyJpIjoiNTIzZW... ) Upgrade Narayana used for integration testing to version 6.0.0.CR1 ( https://hibernate.atlassian.net/browse/HHH-16060?atlOrigin=eyJpIjoiNTIzZW... ) Issue Type: Task Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: testsuite Created: 19/Jan/2023 04:00 AM Fix Versions: 6.2.0 Labels: transaction_manager Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The Narayana project released 6.0.0.CR1, and this release is “Jakarta native”. Would be good to switch our integration tests to use this one. ( https://hibernate.atlassian.net/browse/HHH-16060#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16060#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15921) @BatchSize and @IdClass on join column throws exception

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16031) @ManyToMany with @JoinTable(inverseColumn = ...) and SortedSet may results in data loss

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16031) @ManyToMany with @JoinTable(inverseColumn = ...) and SortedSet may results in data loss

by Andrea Boriero (JIRA)

2 years, 11 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 Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16009 ( https://hibernate.atlassian.net/browse/HHH-16009?atlOrigin=eyJpIjoiNDA0ZW... ) 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=eyJpIjoiNDA0ZW... ) Hello, could you please provide a test case reproducing the issue using only Hibernate and not Spring? https://github.com/hibernate/hibernate-test-case-templates ( https://github.com/hibernate/hibernate-test-case-templates ) Thanks. ( 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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16059) Add getters and relax scopes for Cte strategies and handlers

by Davide D'Alto (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16059) Add getters and relax scopes for Cte strategies and handlers

by Davide D'Alto (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16059) Add getters and relax scopes for Cte strategies and handlers

by Davide D'Alto (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15922) MappingException is thrown for @JoinColumn with referencedColumnName on a @SecondaryTable - Composite Key

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-15922 ( https://hibernate.atlassian.net/browse/HHH-15922?atlOrigin=eyJpIjoiM2QxNz... ) Re: MappingException is thrown for @JoinColumn with referencedColumnName on a @SecondaryTable - Composite Key ( https://hibernate.atlassian.net/browse/HHH-15922?atlOrigin=eyJpIjoiM2QxNz... ) Ciao Marco, thank you for clearing up the example. Now both the schema and the error look a lot like https://hibernate.atlassian.net/browse/HHH-15933 ( https://hibernate.atlassian.net/browse/HHH-15933 ). We’re looking into that issue and your problem should be exactly the same. When we fix that I’ll try to run the new test you provided to see if that’s the case. Keep you updated. ( https://hibernate.atlassian.net/browse/HHH-15922#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15922#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#100214- sha1:5a2a1e8 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16058) Removing Environment#getBytecodeProvider

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzcwYWQwNGQ4... ) / Remove Feature ( https://hibernate.atlassian.net/browse/HHH-16058?atlOrigin=eyJpIjoiMzcwYW... ) HHH-16058 ( https://hibernate.atlassian.net/browse/HHH-16058?atlOrigin=eyJpIjoiMzcwYW... ) Removing Environment#getBytecodeProvider ( https://hibernate.atlassian.net/browse/HHH-16058?atlOrigin=eyJpIjoiMzcwYW... ) Issue Type: Remove Feature Assignee: Unassigned Components: hibernate-core Created: 18/Jan/2023 14:56 PM Fix Versions: 6.2.0 Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Remove the deprecated method Environment.getBytecodeProvider() , ensuring all choices related to the BytecodeProvider are fully scoped into each SessionFactory instance. This effectively makes it possible to use a different BytecodeProvider in each SessionFactory, something which previosly wasn’t possible. A potential follow-up could be to physically separate the BytecodeProvider implementations into an optional jar, and make implementations pluggable/swappable; for GraalVM it’s useful to be able to run the system without actually having any of them reachable. This is a follow-up to https://hibernate.atlassian.net/browse/HHH-12194 ( https://hibernate.atlassian.net/browse/HHH-12194 ) ( https://hibernate.atlassian.net/browse/HHH-16058#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16058#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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16020) Hibernate doesn't set the correct bind parameter for the offset when using NativeQuery.setFirstResult() on Postgresql

by Jan Schatteman (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HV-1935) Test Hibernate Validator against JDK 21

by Guillaume Smet (JIRA)

2 years, 11 months

1
0
0 / 0

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

by Christoph Watzl (JIRA)

Christoph Watzl ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16007 ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiMjA0OT... ) Re: PropertyAccessException when deleting entities with Embeddables with child collections ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiMjA0OT... ) Huh, aparently no longer reproducible in current main branch. Still reproducible in 6.2.0-CR1, though. ( 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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4642) Upgrade build dependencies to the latest version in 6.2.0.Alpha2

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16007) PropertyAccessException when deleting entities 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=eyJpIjoiODMxZjFhMjUw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiODMxZj... ) HHH-16007 ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiODMxZj... ) PropertyAccessException when deleting entities with Embeddables with child collections ( https://hibernate.atlassian.net/browse/HHH-16007?atlOrigin=eyJpIjoiODMxZj... ) 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 an [example test |https://github.com/cwatzl/hhh-16007]project to demonstrate the issue. 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} *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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

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

by Christoph Watzl (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13242) Allow usage of custom BytecodeProvider

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13242 ( https://hibernate.atlassian.net/browse/HHH-13242?atlOrigin=eyJpIjoiNjY4Nm... ) Re: Allow usage of custom BytecodeProvider ( https://hibernate.atlassian.net/browse/HHH-13242?atlOrigin=eyJpIjoiNjY4Nm... ) I’ll be working on some cleanups and clarifications in this regard as follow-up issues. Once that’s clearer we might consider allowing to use a custom one, but I’m not persuaded about the merits of such an idea: so not saying that we’ll do it, but I’m open to talk about it. ( https://hibernate.atlassian.net/browse/HHH-13242#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13242#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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13242) Allow usage of custom BytecodeProvider

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13242) Allow usage of custom BytecodeProvider

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13242) Allow usage of custom BytecodeProvider

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13242) Allow usage of custom BytecodeProvider

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13242 ( https://hibernate.atlassian.net/browse/HHH-13242?atlOrigin=eyJpIjoiNDQ3Nm... ) Re: Allow usage of custom BytecodeProvider ( https://hibernate.atlassian.net/browse/HHH-13242?atlOrigin=eyJpIjoiNDQ3Nm... ) Good point, I’m not sure why it’s marked as “fixed” either. I’ll clarify the state, I think this had been rejected. ( https://hibernate.atlassian.net/browse/HHH-13242#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13242#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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16057) PreUpdate entity listener is broken with runtime bytecode enhancement

by Judit Gera-Kapinya (JIRA)

Judit Gera-Kapinya ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDU5MmM5ZjNm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16057?atlOrigin=eyJpIjoiMDU5Mm... ) HHH-16057 ( https://hibernate.atlassian.net/browse/HHH-16057?atlOrigin=eyJpIjoiMDU5Mm... ) PreUpdate entity listener is broken with runtime bytecode enhancement ( https://hibernate.atlassian.net/browse/HHH-16057?atlOrigin=eyJpIjoiMDU5Mm... ) Issue Type: Bug Affects Versions: 5.6.14 Assignee: Unassigned Attachments: reproducer.zip Components: bytecode-enhancement Created: 18/Jan/2023 05:24 AM Priority: Major Reporter: Judit Gera-Kapinya ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) PreUpdate should be called only if the data was actually changed. In 5.6.14 it is called, even if it was not changed. Worked in 5.6.9. It seems that due to https://hibernate.atlassian.net/browse/HHH-15641 ( https://hibernate.atlassian.net/browse/HHH-15641 ) the byte code enhancement cannot be switched off. Please find a very basic reproducer project attached. ( https://hibernate.atlassian.net/browse/HHH-16057#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16057#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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15917) Migration to 6.X. Unrelated Entity Join Exception

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15917 ( https://hibernate.atlassian.net/browse/HHH-15917?atlOrigin=eyJpIjoiMmY4OW... ) Re: Migration to 6.X. Unrelated Entity Join Exception ( https://hibernate.atlassian.net/browse/HHH-15917?atlOrigin=eyJpIjoiMmY4OW... ) Hi Алексадр Рутковский ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b9117a... ) can you please provide a reproducer if possible using only hibernate? It would be really helpful . here ( https://github.com/hibernate/hibernate-test-case-templates/tree/main/orm ) you can find a template to facilitate the creation of a reproducer. Thanks ( https://hibernate.atlassian.net/browse/HHH-15917#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15917#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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4395) Switch to ORM 6 as the default ORM version and drop support for ORM 5

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiZjM3ZTMz... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4395?atlOrigin=eyJpIjoiZjM... ) HSEARCH-4395 ( https://hibernate.atlassian.net/browse/HSEARCH-4395?atlOrigin=eyJpIjoiZjM... ) Switch to ORM 6 as the default ORM version and drop support for ORM 5 ( https://hibernate.atlassian.net/browse/HSEARCH-4395?atlOrigin=eyJpIjoiZjM... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Requires [https://hibernate.atlassian.net/browse/HSEARCH-4394|https://hibernate.atl...], [https://hibernate.atlassian.net/browse/HSEARCH-3277|https://hibernate.atl...] We will need ORM 6 to provide Java EE artifacts first; at the moment it doesn’t. Before this change: * The main artifacts (no particular suffix, e.g. {{hibernate-search-mapper-orm}}) target Hibernate ORM 5.x * There are additional artifacts with a '-javaee' suffix (e.g. {{hibernate-search-mapper-javaee}}) to support Hibernate ORM 5.x + Java EE * There are additional artifacts with a '-orm6' suffix (e.g. {{hibernate-search-mapper-orm6}}) to support Hibernate ORM 6.x + Jakarta EE After this change: * The main artifacts (no particular suffix, e.g. {{hibernate-search-mapper-orm}}) target Hibernate ORM 6.x and Jakarta EE * There are *no* additional artifacts to support ORM 5.x * There are *no* additional artifacts to support Java EE * There are relocation artifacts for the artifacts with a '- javaee orm6 ' suffix (e.g. {{hibernate-search-mapper- javaee orm6 }}) to support cater to application server users (e.g. WildFly) when their application server upgrades from Hibernate ORM Search 6.x + Java EE * There are *no* additional to 7 and switches from -orm6 artifacts to support ORM 5.x the main artifacts ( https://hibernate.atlassian.net/browse/HSEARCH-4395#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4395#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#100214- sha1:0a999ef )

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4787) Upgrade to Mockito 5

by Marko Bekhta (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HV-1935) Test Hibernate Validator against JDK 21

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HV-1935) Test Hibernate Validator against JDK 21

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4780) Test Hibernate Search against JDK 21

by Automation for Jira (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16054) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key

by Cui Pengfei (JIRA)

Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzFkYmU3MDI3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiMzFkYm... ) HHH-16054 ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiMzFkYm... ) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiMzFkYm... ) Change By: Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) # h1. How to reproduce this issue <strike> [- https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue ~~ -|https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue] - this code can reproduce the issue, just run the main method then the error will happen. </strike> - [ https://github.com/gregturn/spring-data-jpa-id-class-issues/tree/main/src... |https://github.com/gregturn/spring-data-jpa-id-class-issues/tree/main/src/test/java/com/example/demo|smart-link] Just make sure you have docker installed and run these 👆 unit tests. The unit test with * * EmbeddedId* * will be ok. But the one with * * IdClass* * will * * fail* * , while we * * expect* * it to be * * successful* *. h1. Issue Description There is a base class like this: {code:java} @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorFormula("case when vip_number is not null then 'vip' else 'normal' end") @DiscriminatorValue("normal") @IdClass(CustomerPK.class) public class CustomerWithIdClass implements Serializable { private String firstName; private String lastName; @Id private Long versionId; @Id private Long unitId; protected CustomerWithIdClass() { } // getter and setters ...... }{code} Its IdClass is like this: {code:java}@NoArgsConstructor @EqualsAndHashCode @Embeddable public class CustomerPK implements Serializable { private Long unitId; private Long versionId; public void setUnitId(Long unitId) { this.unitId = unitId; } public void setVersionId(Long versionId) { this.versionId = versionId; } }{code} Then it has a subclass: {code:java}@Entity @DiscriminatorValue("vip") public class VipCustomerWithIdClass extends CustomerWithIdClass { private String vipNumber; public VipCustomerWithIdClass() { } public VipCustomerWithIdClass(String firstName, String lastName, String vipNumber) { super(firstName, lastName); this.vipNumber = vipNumber; } public String getVipNumber() { return vipNumber; } public void setVipNumber(String vipNumber) { this.vipNumber = vipNumber; } } {code} The subclass only adds one additional field, nothing else fancy. Then when I try to persist an instance of the subclass like this: {code:java} CustomerWithIdClass customer = new CustomerWithIdClass("a", "b"); customer.setVersionId(123L); customer.setUnitId(456L); repository.save(customer);//save object of base class, ok customer.setFirstName("a2"); repository.save(customer);//modify object of base class and save again, ok VipCustomerWithIdClass vipCustomer = new VipCustomerWithIdClass("a", "b", "888"); vipCustomer.setVersionId(987L); vipCustomer.setUnitId(654L); repository.save(vipCustomer);//save object of subclass, ok vipCustomer.setVipNumber("999"); repository.save(vipCustomer);//modify object of subclass and save again, NOT OK // ↑ THIS FAILS BECAUSE OF PRIMARY KEY CONFLICT. INSERT STATEMENT WAS USED INSTEAD OF UPDATE, WHY? // this failure only happens when: // 1. base class uses IdClass for composite primary key // 2. saving an instance of the subclass for the second time after modification {code} h1. The Error Then there will be an *error of duplicate pkey* when I try to save the instance of the *subclass* for the *second time* *after some modification*. The error seems to be related with the @*IdClass* annotation, because I have tried using @*EmbeddedId* and @*Embeddable* for composite pkey, then the error does not happen. h1. The question What is the root reason of this issue? Is @IdClass not supposed to be used for this scenario? h1. links [https://stackoverflow.com/questions/75147518/jpa-hibernate-duplicate-pkey...] [https://github.com/spring-projects/spring-data-jpa/issues/2767|https://gi...] ( https://hibernate.atlassian.net/browse/HHH-16054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16054#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16054) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key

by Cui Pengfei (JIRA)

Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDQxY2UyNGQw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiNDQxY2... ) HHH-16054 ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiNDQxY2... ) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiNDQxY2... ) Change By: Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. # How to reproduce this issue [ <strike> https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue |https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue|smart-link] ~~ this code can reproduce the issue, just run the main method then the error will happen. </strike> https://github.com/gregturn/spring-data-jpa-id-class-issues/tree/main/src... Just make sure you have docker installed and run these 👆 unit tests. The unit test with **EmbeddedId** will be ok. But the one with **IdClass** will **fail**, while we **expect** it to be **successful**. h1. Issue Description There is a base class like this: {code:java} @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorFormula("case when vip_number is not null then 'vip' else 'normal' end") @DiscriminatorValue("normal") @IdClass(CustomerPK.class) public class CustomerWithIdClass implements Serializable { private String firstName; private String lastName; @Id private Long versionId; @Id private Long unitId; protected CustomerWithIdClass() { } // getter and setters ...... }{code} Its IdClass is like this: {code:java}@NoArgsConstructor @EqualsAndHashCode @Embeddable public class CustomerPK implements Serializable { private Long unitId; private Long versionId; public void setUnitId(Long unitId) { this.unitId = unitId; } public void setVersionId(Long versionId) { this.versionId = versionId; } }{code} Then it has a subclass: {code:java}@Entity @DiscriminatorValue("vip") public class VipCustomerWithIdClass extends CustomerWithIdClass { private String vipNumber; public VipCustomerWithIdClass() { } public VipCustomerWithIdClass(String firstName, String lastName, String vipNumber) { super(firstName, lastName); this.vipNumber = vipNumber; } public String getVipNumber() { return vipNumber; } public void setVipNumber(String vipNumber) { this.vipNumber = vipNumber; } } {code} The subclass only adds one additional field, nothing else fancy. Then when I try to persist an instance of the subclass like this: {code:java} CustomerWithIdClass customer = new CustomerWithIdClass("a", "b"); customer.setVersionId(123L); customer.setUnitId(456L); repository.save(customer);//save object of base class, ok customer.setFirstName("a2"); repository.save(customer);//modify object of base class and save again, ok VipCustomerWithIdClass vipCustomer = new VipCustomerWithIdClass("a", "b", "888"); vipCustomer.setVersionId(987L); vipCustomer.setUnitId(654L); repository.save(vipCustomer);//save object of subclass, ok vipCustomer.setVipNumber("999"); repository.save(vipCustomer);//modify object of subclass and save again, NOT OK // ↑ THIS FAILS BECAUSE OF PRIMARY KEY CONFLICT. INSERT STATEMENT WAS USED INSTEAD OF UPDATE, WHY? // this failure only happens when: // 1. base class uses IdClass for composite primary key // 2. saving an instance of the subclass for the second time after modification {code} h1. The Error Then there will be an *error of duplicate pkey* when I try to save the instance of the *subclass* for the *second time* *after some modification*. The error seems to be related with the @*IdClass* annotation, because I have tried using @*EmbeddedId* and @*Embeddable* for composite pkey, then the error does not happen. h1. The question What is the root reason of this issue? Is @IdClass not supposed to be used for this scenario? h1. links [https://stackoverflow.com/questions/75147518/jpa-hibernate-duplicate-pkey...] [https://github.com/spring-projects/spring-data-jpa/issues/2767|https://gi...] ( https://hibernate.atlassian.net/browse/HHH-16054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16054#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16056) Pessimistic write lock does not always return latest database state

by pioneer.vvs＠gmail.com (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16055) Again - Refreshing an entity clears the lock mode returned from EntityManager.getLockMode

by pioneer.vvs＠gmail.com (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-12257) Refreshing an entity clears the lock mode returned from EntityManager.getLockMode

by Rustam Anvarov (JIRA)

Rustam Anvarov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b69406... ) *commented* on HHH-12257 ( https://hibernate.atlassian.net/browse/HHH-12257?atlOrigin=eyJpIjoiM2JiMW... ) Re: Refreshing an entity clears the lock mode returned from EntityManager.getLockMode ( https://hibernate.atlassian.net/browse/HHH-12257?atlOrigin=eyJpIjoiM2JiMW... ) Hey guys, this error persists in 5.3.0 - 5.6.0, please re-open this case ( https://hibernate.atlassian.net/browse/HHH-12257#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-12257#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16052) EntityKey and CollectionKey equality optimisation

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16023) ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1 for NamedNativeQuery with generics

by Marco Belladelli (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16023) ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1 (with added test case)

by Marco Belladelli (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15972) entitygraph load error when Inheritance JOINED is used in 6.1.6

by Theodoros Papatheodorou (JIRA)

Theodoros Papatheodorou ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODZlMjc0MGVk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15972?atlOrigin=eyJpIjoiODZlMj... ) HHH-15972 ( https://hibernate.atlassian.net/browse/HHH-15972?atlOrigin=eyJpIjoiODZlMj... ) entitygraph load error when Inheritance JOINED is used in 6.1.6 ( https://hibernate.atlassian.net/browse/HHH-15972?atlOrigin=eyJpIjoiODZlMj... ) Change By: Theodoros Papatheodorou ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) Exception occurs with the use of entitygraph loadgraph in case InheritanceType.JOINED is used and the parent class is queried (testcase attached). {noformat}java.lang.IllegalArgumentException: org.hibernate.query.SemanticException: Could not resolve attribute 'status' of 'org.hibernate.bugs.Account' due to the attribute being declared in multiple sub types: ['org.hibernate.bugs.Account1', 'org.hibernate.bugs.Account2'] at org.hibernate.metamodel.model.domain.AbstractManagedType.findAttribute(AbstractManagedType.java:178) at org.hibernate.metamodel.model.domain.internal.EntityTypeImpl.findAttribute(EntityTypeImpl.java:143) at org.hibernate.graph.internal.AbstractGraph.findAttributeNode(AbstractGraph.java:142) at org.hibernate.sql.results.internal.StandardEntityGraphTraversalStateImpl.traverse(StandardEntityGraphTraversalStateImpl.java:54) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.addFetch(BaseSqmToSqlAstConverter.java:6937) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitFetches(BaseSqmToSqlAstConverter.java:7099) at org.hibernate.sql.results.graph.AbstractFetchParent.afterInitialize(AbstractFetchParent.java:32) at org.hibernate.sql.results.graph.entity.AbstractEntityResultGraphNode.afterInitialize(AbstractEntityResultGraphNode.java:100) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.createDomainResult(JoinedSubclassEntityPersister.java:1225) at org.hibernate.query.sqm.sql.internal.AbstractSqmPathInterpretation.createDomainResult(AbstractSqmPathInterpretation.java:55) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.lambda$visitSelection$25(BaseSqmToSqlAstConverter.java:2053) at java.base/java.util.Collections$SingletonList.forEach(Collections.java:4966) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitSelection(BaseSqmToSqlAstConverter.java:2048) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitSelectClause(BaseSqmToSqlAstConverter.java:1951) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitQuerySpec(BaseSqmToSqlAstConverter.java:1819) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitQuerySpec(BaseSqmToSqlAstConverter.java:416) at org.hibernate.query.sqm.tree.select.SqmQuerySpec.accept(SqmQuerySpec.java:122) at org.hibernate.query.sqm.spi.BaseSemanticQueryWalker.visitQueryPart(BaseSemanticQueryWalker.java:213) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitQueryPart(BaseSqmToSqlAstConverter.java:1679) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitSelectStatement(BaseSqmToSqlAstConverter.java:1477) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.visitSelectStatement(BaseSqmToSqlAstConverter.java:416) at org.hibernate.query.sqm.tree.select.SqmSelectStatement.accept(SqmSelectStatement.java:213) at org.hibernate.query.sqm.sql.BaseSqmToSqlAstConverter.translate(BaseSqmToSqlAstConverter.java:711) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.buildCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:380) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:300) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:276) at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:571) at org.hibernate.query.spi.AbstractSelectionQuery.list(AbstractSelectionQuery.java:363) at org.hibernate.query.sqm.internal.QuerySqmImpl.list(QuerySqmImpl.java:1073) at org.hibernate.query.Query.getResultList(Query.java:94) at org.hibernate.bugs.JPAUnitTestCase.hhh123Test(JPAUnitTestCase.java: 89 70 ) 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.query.SemanticException: Could not resolve attribute 'status' of 'org.hibernate.bugs.Account' due to the attribute being declared in multiple sub types: ['org.hibernate.bugs.Account1', 'org.hibernate.bugs.Account2'] ... 60 more {noformat} ( https://hibernate.atlassian.net/browse/HHH-15972#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15972#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15972) entitygraph load error when Inheritance JOINED is used in 6.1.6

by Theodoros Papatheodorou (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15972) entitygraph load error when Inheritance JOINED is used in 6.1.6

by Theodoros Papatheodorou (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-15972) entitygraph load error in 6.1.6

by Theodoros Papatheodorou (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16054) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key

by Cui Pengfei (JIRA)

Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmNkMjVmYjU3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiMmNkMj... ) HHH-16054 ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiMmNkMj... ) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiMmNkMj... ) Change By: Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. How to reproduce this issue [https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue|h...] this code can reproduce the issue, just run the main method then the error will happen. h1. Issue Description There is a base class like this: {code:java} @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorFormula("case when vip_number is not null then 'vip' else 'normal' end") @DiscriminatorValue("normal") @IdClass(CustomerPK.class) public class CustomerWithIdClass implements Serializable { private String firstName; private String lastName; @Id private Long versionId; @Id private Long unitId; protected CustomerWithIdClass() { } // getter and setters ...... }{code} Its IdClass is like this: {code:java}@NoArgsConstructor @EqualsAndHashCode @Embeddable public class CustomerPK implements Serializable { private Long unitId; private Long versionId; public void setUnitId(Long unitId) { this.unitId = unitId; } public void setVersionId(Long versionId) { this.versionId = versionId; } }{code} Then it has a subclass: {code:java}@Entity @DiscriminatorValue("vip") public class VipCustomerWithIdClass extends CustomerWithIdClass { private String vipNumber; public VipCustomerWithIdClass() { } public VipCustomerWithIdClass(String firstName, String lastName, String vipNumber) { super(firstName, lastName); this.vipNumber = vipNumber; } public String getVipNumber() { return vipNumber; } public void setVipNumber(String vipNumber) { this.vipNumber = vipNumber; } } {code} The subclass only adds one additional field, nothing else fancy. Then when I try to persist an instance of the subclass like this: {code:java} CustomerWithIdClass customer = new CustomerWithIdClass("a", "b"); customer.setVersionId(123L); customer.setUnitId(456L); repository.save(customer);//save object of base class, ok customer.setFirstName("a2"); repository.save(customer);//modify object of base class and save again, ok VipCustomerWithIdClass vipCustomer = new VipCustomerWithIdClass("a", "b", "888"); vipCustomer.setVersionId(987L); vipCustomer.setUnitId(654L); repository.save(vipCustomer);//save object of subclass, ok vipCustomer.setVipNumber("999"); repository.save(vipCustomer);//modify object of subclass and save again, NOT OK // ↑ THIS FAILS BECAUSE OF PRIMARY KEY CONFLICT. INSERT STATEMENT WAS USED INSTEAD OF UPDATE, WHY? // this failure only happens when: // 1. base class uses IdClass for composite primary key // 2. saving an instance of the subclass for the second time after modification {code} h1. The Error Then there will be an *error of duplicate pkey* when I try to save the instance of the *subclass* for the *second time* *after some modification*. The error seems to be related with the @*IdClass* annotation, because I have tried using @*EmbeddedId* and @*Embeddable* for composite pkey, then the error does not happen. h1. The question What is the root reason of this issue? Is @IdClass not supposed to be used for this scenario? h1. links [https://stackoverflow.com/questions/75147518/jpa-hibernate-duplicate-pkey...] [https://github.com/spring-projects/spring-data-jpa/issues/2767|https://gi...] ( https://hibernate.atlassian.net/browse/HHH-16054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16054#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16054) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key

by Cui Pengfei (JIRA)

Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiY2I3NTA4MGY0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiY2I3NT... ) HHH-16054 ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiY2I3NT... ) JPA / Hibernate, duplicate pkey error when updating entity that is a subclass of a base class that uses IdClass for composite primary key ( https://hibernate.atlassian.net/browse/HHH-16054?atlOrigin=eyJpIjoiY2I3NT... ) Issue Type: Bug Affects Versions: 5.6.14 Assignee: Unassigned Components: hibernate-core Created: 17/Jan/2023 06:12 AM Environment: Hibernate libraries: hibernate-core-5.6.14.Final.jar hibernate-commons-annotations-5.1.2.Final.jar JVM: openjdk 16 operating system, mac 12.6.2 and windows 10 database platform pg and mysql Priority: Major Reporter: Cui Pengfei ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *************************** How to reproduce this issue *************************** https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue ( https://github.com/cuipengfei/Spikes/tree/master/jpa/ClassIdUpdateIssue ) this code can reproduce the issue, just run the main method then the error will happen. ***************** Issue Description ***************** There is a base class like this: @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorFormula( " case when vip_number is not null then 'vip' else 'normal' end" ) @DiscriminatorValue( "normal" ) @IdClass(CustomerPK.class) public class CustomerWithIdClass implements Serializable { private String firstName; private String lastName; @Id private Long versionId; @Id private Long unitId; protected CustomerWithIdClass() { } // getter and setters ...... } Its IdClass is like this: @NoArgsConstructor @EqualsAndHashCode @Embeddable public class CustomerPK implements Serializable { private Long unitId; private Long versionId; public void setUnitId( Long unitId) { this.unitId = unitId; } public void setVersionId( Long versionId) { this.versionId = versionId; } } Then it has a subclass: @Entity @DiscriminatorValue( "vip" ) public class VipCustomerWithIdClass extends CustomerWithIdClass { private String vipNumber; public VipCustomerWithIdClass() { } public VipCustomerWithIdClass( String firstName, String lastName, String vipNumber) { super (firstName, lastName); this.vipNumber = vipNumber; } public String getVipNumber() { return vipNumber; } public void setVipNumber( String vipNumber) { this.vipNumber = vipNumber; } } The subclass only adds one additional field, nothing else fancy. Then when I try to persist an instance of the subclass like this: CustomerWithIdClass customer = new CustomerWithIdClass( "a" , "b" ); customer.setVersionId(123L); customer.setUnitId(456L); repository.save(customer); //save object of base class, ok customer.setFirstName( "a2" ); repository.save(customer); //modify object of base class and save again, ok VipCustomerWithIdClass vipCustomer = new VipCustomerWithIdClass( "a" , "b" , "888" ); vipCustomer.setVersionId(987L); vipCustomer.setUnitId(654L); repository.save(vipCustomer); //save object of subclass, ok vipCustomer.setVipNumber( "999" ); repository.save(vipCustomer); //modify object of subclass and save again, NOT OK // ↑ THIS FAILS BECAUSE OF PRIMARY KEY CONFLICT. INSERT STATEMENT WAS USED INSTEAD OF UPDATE, WHY? // this failure only happens when: // 1. base class uses IdClass for composite primary key // 2. saving an instance of the subclass for the second time after modification ********* The Error ********* Then there will be an *error of duplicate pkey* when I try to save the instance of the *subclass* for the *second time* *after some modification*. The error seems to be related with the @ *IdClass* annotation, because I have tried using @ *EmbeddedId* and @ *Embeddable* for composite pkey, then the error does not happen. ************ The question ************ What is the root reason of this issue? Is @IdClass not supposed to be used for this scenario? ***** links ***** https://stackoverflow.com/questions/75147518/jpa-hibernate-duplicate-pkey... ( https://stackoverflow.com/questions/75147518/jpa-hibernate-duplicate-pkey... ) ( https://hibernate.atlassian.net/browse/HHH-16054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16054#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4781) Mention @ScaledNumberField in error messages when the decimal scale cannot be found

by Automation for Jira (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inheritance)

by Lukas Witzani (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance)

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGE2NWZlMjQ1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNGE2NW... ) HHH-16053 ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNGE2NW... ) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance) ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNGE2NW... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. Summary * after updating spring boot to 3.0.1 (which also updates hibernate to 6.1.6.Final) join fetching of nested entities does not work anymore when the nestedEntity reference is in an abstract superclass ("BodyPart") that uses @Inheritance(strategy = InheritanceType.SINGLE_TABLE) * the result is a LazyInitializationException when accessing fields in the nested entity although join fetch has been specified in the @Query h2. Requisites * entity ("Person") exists that has a field which is a set of other entities ("Set<Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE * the abstract super class has a nested entity ("NestedEntity") which has some fields !diagram.png|width=614,height=479! h2. Reproduction * [https://github.com/lwitzani/hibernate6JoinFetchIssue|https://github.com/l... are two branches in this repository (one with hibernate 5 and on with hibernate 6) * execute the test PersonPersistenceTest.shouldJoinFetchTheNestedEntitiesOfLegs * the test basically ** creates and saves a Person with one Leg and that Leg has a NestedEntity ** fetches the Person by findByIdJoinFetchLegsWithNestedEntity (a @Query method in the Repository). The query uses join fetch to specify that person->legs is fetched and also that legs->nestedEntity is fetched. ** tries to access the nested entity via person->legs->nestedEntity->name h2. Observations in Hibernate 5.6.14.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is working correct * it join fetches both the body_part and the nested_entity table * it uses a left OUTER join for that * it only defines the clause legs1_.discriminator='LegBodyPart' once !hibernate5_working.png|width=1501,height=926! h2. Observations in Hibernate 6.1.6.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is NOT working correct ** there is no second left join which would join the nested_entity table ** it does NOT use a left join (not outer) ** also, it is strange that there is a duplicate join clause l1_0.discriminator='LegBodyPart' and l1_0.discriminator='LegBodyPart' * result is a LazyInitializationException when accessing the name !hibernate6_failing.png|width=1480,height=926! This issue might be heavily related to [https://hibernate.atlassian.net/browse/HHH-16037|https://hibernate.atlass...] and maybe related to: * [https://hibernate.atlassian.net/browse/HHH-15876|https://hibernate.atlass...] * [https://hibernate.atlassian.net/browse/HHH-15829|https://hibernate.atlass...] ( https://hibernate.atlassian.net/browse/HHH-16053#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16053#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16037) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTJkNTk3ZTZk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMTJkNT... ) HHH-16037 ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMTJkNT... ) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMTJkNT... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. Summary * after updating spring boot to 3.0.1 which also updates hibernate to 6.1.6.Final it does not seem to be possible to update an entity with this constellation * the main difference is that an additional and unexpected where clause is added which prevents finding the correct entity in this case * the result is that a new entity is persisted instead of the existing one being updated h2. Minimal project for reproduction * [https://github.com/lwitzani/hibernate6_singleTableIssue|https://github.co...] * project has two branches (one with hibernate 5 and one with hibernate 6) * the only difference in the branches is the updated versions of spring boot and therefore hibernate * i debugged very deep and think that it is a problem with hibernate at the location where the select statement is generated ({{LoaderSelectBuilder}}.{{createSelect}}) h2. Requisites * entity ("Person") exists that has a field which is a set of other entities ("Set<Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE !uml.png|width=517,height=425! h2. Reproduction * execute the test PersonPersistenceTest.shouldUseSQLUpdateToChangeThePersonName * the test basically ** creates a Person (without Legs) and saves it using the repository ** refetches the Person by findById ** changes the Person's name ** saves the changed Person again h2. Observations in Hibernate 5.6.14.Final * when the second save is called (after changing the name) there will be a select statement which is used to check if the entity already exists ** the body_part table is joined via left outer join ** the where clause here only consists of "where [person.id|http://person.id] = <id>" * the entity is correctly found by the select statement so afterwards an update statement follows * result: one entity exists (the changed one) !hibernate5.png|width=1265,height=692! h2. Observations in Hibernate 6.1.6.Final * when the second save is called (after changing the name) there will be a different select statement now ** the body_part table is joined via left join now (not outer) ** the critical change here is that the where clause now suddenly consists of "where body_part.discriminator = 'LegBodyPart' and [person.id|http://person.id] = <id>" * although the entity exists, it is not found by the select statement so afterwards an insert statement follows which creates a second Person with a new id * result: two entities exist (the original one and the changed one) !hibernate6.png|width=1179,height=644! h1. Summary * after updating spring boot This issue might be heavily related to 3 [https://hibernate. 0 atlassian. 1 which also updates net/browse/HHH-16053|https:// hibernate to 6. 1 atlassian. 6.Final it does not seem to be possible to update an entity with this constellation net/browse/HHH-16053|smart-link] * the main difference is that an additional and unexpected where clause is added which prevents finding the correct entity in this case maybe related to: * the result is that a new entity is persisted instead of the existing one being updated [https://hibernate.atlassian.net/browse/HHH-15876|https://hibernate.atlass...] * [https://hibernate.atlassian.net/browse/HHH-15829|https://hibernate.atlass...] ( https://hibernate.atlassian.net/browse/HHH-16037#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16037#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance)

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmYzMGM3NDhl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiMmYzMG... ) HHH-16053 ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiMmYzMG... ) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance) ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiMmYzMG... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h1. Summary * after updating spring boot to 3.0.1 (which also updates hibernate to 6.1.6.Final) join fetching of nested entities does not work anymore when the nestedEntity reference is in an abstract superclass ("BodyPart") that uses @Inheritance(strategy = InheritanceType.SINGLE_TABLE) * the result is a LazyInitializationException when accessing fields in the nested entity although join fetch has been specified in the @Query h2. Requisites * entity ("Person") exists that has a field which is a set of other entities ("Set<Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE * the abstract super class has a nested entity ("NestedEntity") which has some fields !diagram.png|width=614,height=479! h2. Reproduction * [https://github.com/lwitzani/hibernate6JoinFetchIssue|https://github.com/l... are two branches in this repository (one with hibernate 5 and on with hibernate 6) * execute the test PersonPersistenceTest.shouldJoinFetchTheNestedEntitiesOfLegs * the test basically ** creates and saves a Person with one Leg and that Leg has a NestedEntity ** fetches the Person by findByIdJoinFetchLegsWithNestedEntity (a @Query method in the Repository). The query uses join fetch to specify that person->legs is fetched and also that legs->nestedEntity is fetched. ** tries to access the nested entity via person->legs->nestedEntity->name h2. Observations in Hibernate 5.6.14.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is working correct * it join fetches both the body_part and the nested_entity table * it uses a left OUTER join for that * it only defines the clause legs1_.discriminator='LegBodyPart' once !hibernate5_working.png|width=1501,height=926! h2. Observations in Hibernate 6.1.6.Final * the query created by findByIdJoinFetchLegsWithNestedEntity is NOT working correct ** there is no second left join which would join the nested_entity table ** it does NOT use a left join (not outer) ** also, it is strange that there is a duplicate join clause l1_0.discriminator='LegBodyPart' and l1_0.discriminator='LegBodyPart' * result is a LazyInitializationException when accessing the name !hibernate6_failing.png|width=1480,height=926! This issue might be heavily related to [https://hibernate.atlassian.net/browse/HHH-16037|https://hibernate.atlass...] and maybe related to: * [https://hibernate.atlassian.net/browse/HHH-15876|https://hibernate.atlass...] * [https://hibernate.atlassian.net/browse/HHH-15829|https://hibernate.atlass...] ( https://hibernate.atlassian.net/browse/HHH-16053#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16053#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16053) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance)

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTVmZWE4NWVm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNTVmZW... ) HHH-16053 ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNTVmZW... ) join fetch in @Query has no effect for for nested entities with @DiscriminatorValue (SINGLE_TABLE inhertitance) ( https://hibernate.atlassian.net/browse/HHH-16053?atlOrigin=eyJpIjoiNTVmZW... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Attachments: diagram.png, hibernate5_working.png, hibernate6_failing.png Components: hibernate-core Created: 17/Jan/2023 05:30 AM Environment: Java 17 Spring Boot 3.0.1 Priority: Major Reporter: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) ******* Summary ******* * after updating spring boot to 3.0.1 (which also updates hibernate to 6.1.6.Final) join fetching of nested entities does not work anymore when the nestedEntity reference is in an abstract superclass ("BodyPart") that uses @Inheritance(strategy = InheritanceType.SINGLE_TABLE) * the result is a LazyInitializationException when accessing fields in the nested entity although join fetch has been specified in the @Query ---------- Requisites ---------- * entity ("Person") exists that has a field which is a set of other entities ("Set<Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE * the abstract super class has a nested entity ("NestedEntity") which has some fields ------------ Reproduction ------------ * https://github.com/lwitzani/hibernate6JoinFetchIssue ( https://github.com/lwitzani/hibernate6JoinFetchIssue ) there are two branches in this repository (one with hibernate 5 and on with hibernate 6) * execute the test PersonPersistenceTest.shouldJoinFetchTheNestedEntitiesOfLegs * the test basically * creates and saves a Person with one Leg and that Leg has a NestedEntity * fetches the Person by findByIdJoinFetchLegsWithNestedEntity (a @Query method in the Repository). The query uses join fetch to specify that person->legs is fetched and also that legs->nestedEntity is fetched. * tries to access the nested entity via person->legs->nestedEntity->name -------------------------------------- Observations in Hibernate 5.6.14.Final -------------------------------------- * the query created by findByIdJoinFetchLegsWithNestedEntity is working correct * it join fetches both the body_part and the nested_entity table * it uses a left OUTER join for that * it only defines the clause legs1_.discriminator='LegBodyPart' once ( https://hibernate.atlassian.net/secure/attachment/50171/50171_hibernate5_... ) ------------------------------------- Observations in Hibernate 6.1.6.Final ------------------------------------- * the query created by findByIdJoinFetchLegsWithNestedEntity is NOT working correct * there is no second left join which would join the nested_entity table * it does NOT use a left join (not outer) * also, it is strange that there is a duplicate join clause l1_0.discriminator='LegBodyPart' and l1_0.discriminator='LegBodyPart' * result is a LazyInitializationException when accessing the name ( https://hibernate.atlassian.net/secure/attachment/50172/50172_hibernate6_... ) ( https://hibernate.atlassian.net/browse/HHH-16053#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16053#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HV-1934) Upgrade to hibernate-asciidoctor-theme 1.0.6

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HV-1744) Use auto-expanding entries in the documentation TOC

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16052) EntityKey and CollectionKey equality optimisation

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiY2VkOGJiZjBm... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16052?atlOrigin=eyJpIjoiY2VkOG... ) HHH-16052 ( https://hibernate.atlassian.net/browse/HHH-16052?atlOrigin=eyJpIjoiY2VkOG... ) EntityKey and CollectionKey equality optimisation ( https://hibernate.atlassian.net/browse/HHH-16052?atlOrigin=eyJpIjoiY2VkOG... ) Issue Type: Improvement Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-core Created: 17/Jan/2023 03:20 AM Environment: Since IdentifierType#isEqual is a megamorphic operation, it's worthwhile attempting to avoid the operation when there's good chances that the IDs are actually the same. This is a fairly common operation and has shown beneficial impact on general performance. Fix Versions: 6.2.0 Labels: performance Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) ( https://hibernate.atlassian.net/browse/HHH-16052#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16052#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4786) Fix non-compiling code in migration guide

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4786) Fix non-compiling code in migration guide

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16049) Setting a property to its current value with bytecode enhancement enabled results in unnecessary SQL Update in some (many) cases

by Andrea Boriero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-638) Broken link: https://hibernate.org/orm/domain-model/

by Yoann Rodière (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-638) Broken link: https://hibernate.org/orm/domain-model/

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on WEBSITE-638 ( https://hibernate.atlassian.net/browse/WEBSITE-638?atlOrigin=eyJpIjoiMmZl... ) Re: Broken link: https://hibernate.org/orm/domain-model/ ( https://hibernate.atlassian.net/browse/WEBSITE-638?atlOrigin=eyJpIjoiMmZl... ) No result on the wayback machine: http://web.archive.org/web/*/http://hibernate.org/orm/domain-model/* ( http://web.archive.org/web/*/http://hibernate.org/orm/domain-model/* ) As far as I’m concerned, that link has never worked. Closing. ( https://hibernate.atlassian.net/browse/WEBSITE-638#add-comment?atlOrigin=... ) Add Comment ( https://hibernate.atlassian.net/browse/WEBSITE-638#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#100214- sha1:771690a )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16051) Avoid stateful lambdas on invocations of Stack#findCurrentFirst

by Sanne Grinovero (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16051) Avoid stateful lambdas on invocations of Stack#findCurrentFirst

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiM2YyYTVlYWY3... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16051?atlOrigin=eyJpIjoiM2YyYT... ) HHH-16051 ( https://hibernate.atlassian.net/browse/HHH-16051?atlOrigin=eyJpIjoiM2YyYT... ) Avoid stateful lambdas on invocations of Stack#findCurrentFirst ( https://hibernate.atlassian.net/browse/HHH-16051?atlOrigin=eyJpIjoiM2YyYT... ) Issue Type: Improvement Assignee: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-core Created: 16/Jan/2023 12:37 PM Fix Versions: 6.2.0 Labels: performance Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We have a number of cases in which findCurrentFirst on the internal Stack implementation need to pass an additional parameter, leading to functions passed to it needing to be stateful (aka “capturing lambdas”). For efficiency reasons it would be much better to avoid such lambdas and expose instead a specialized method which allows passing an additional parameter, and consume it again by definig a BiFunction instead of a Function. ( https://hibernate.atlassian.net/browse/HHH-16051#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16051#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#100214- sha1:bdfa1eb )

2 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-638) Broken link: https://hibernate.org/orm/domain-model/

by Website Form collector (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16050) Optimize iteration efficiency in StandardStack

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTM1ODg0ODc4... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16050?atlOrigin=eyJpIjoiMTM1OD... ) HHH-16050 ( https://hibernate.atlassian.net/browse/HHH-16050?atlOrigin=eyJpIjoiMTM1OD... ) Optimize iteration efficiency in StandardStack ( https://hibernate.atlassian.net/browse/HHH-16050?atlOrigin=eyJpIjoiMTM1OD... ) Issue Type: Improvement Assignee: Unassigned Created: 16/Jan/2023 10:04 AM Fix Versions: 6.wishlist Labels: performance Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The StandardStack implementation we have could use some extra care in how findCurrentFirst is currently implemented : iteration is intensive and we could avoid allocating the iterator by switching to a direct array implementation. This would also save some memory in allocating the StandardStack instance by “inlining” its internals. ( https://hibernate.atlassian.net/browse/HHH-16050#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16050#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#100214- sha1:bdfa1eb )

2 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-4774) Database deadlock while processing events with MS SQL Server

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4774 ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiNDU... ) Re: Database deadlock while processing events with MS SQL Server ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiNDU... ) Another failure, I didn’t look in details though: https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/deta... ( https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/deta... ) ( https://hibernate.atlassian.net/browse/HSEARCH-4774#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4774#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#100214- sha1:bdfa1eb )

2 years, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4774) Database deadlock while processing events with MS SQL Server

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMzg4YzA4... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiMzg... ) HSEARCH-4774 ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiMzg... ) Database deadlock while processing events with MS SQL Server ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiMzg... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Encountered on CI: [https://ci.hibernate.org/job/hibernate-search/job/main/549/testReport/jun... ], [https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/deta... | https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/deta... smart-link] {{org.hibernate.search.integrationtest.mapper.orm.coordination.outboxpolling.automaticindexing.OutboxPollingAutomaticIndexingConcurrencyIT(coord-outbox-default-database-mssql).noDeadlock}} {noformat}19:13:58,809 (Hibernate Search - Outbox event processor - 0) ERROR LogFailureHandler:31 - HSEARCH000058: Exception occurred javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query Failing operation: Executing task 'Outbox event processor' javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1626) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.search.mapper.orm.coordination.outboxpolling.event.impl.DefaultOutboxEventFinder.findOutboxEvents(DefaultOutboxEventFinder.java:61) ~[hibernate-search-mapper-orm-coordination-outbox-polling-6.2.0-SNAPSHOT.jar:6.2.0-SNAPSHOT] at org.hibernate.search.mapper.orm.coordination.outboxpolling.event.impl.OutboxPollingEventProcessor$Worker.lambda$work$0(OutboxPollingEventProcessor.java:252) ~[hibernate-search-mapper-orm-coordination-outbox-polling-6.2.0-SNAPSHOT.jar:6.2.0-SNAPSHOT] at org.hibernate.search.mapper.orm.common.spi.TransactionHelper.inTransaction(TransactionHelper.java:54) ~[hibernate-search-mapper-orm-6.2.0-SNAPSHOT.jar:6.2.0-SNAPSHOT] at org.hibernate.search.mapper.orm.coordination.outboxpolling.event.impl.OutboxPollingEventProcessor$Worker.work(OutboxPollingEventProcessor.java:244) ~[hibernate-search-mapper-orm-coordination-outbox-polling-6.2.0-SNAPSHOT.jar:6.2.0-SNAPSHOT] at org.hibernate.search.engine.backend.orchestration.spi.SingletonTask$RunnableWrapper.run(SingletonTask.java:199) ~[hibernate-search-engine-6.2.0-SNAPSHOT.jar:6.2.0-SNAPSHOT] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?] at java.lang.Thread.run(Thread.java:833) ~[?:?] Caused by: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.doList(Loader.java:2871) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.doList(Loader.java:2850) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2682) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.list(Loader.java:2677) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:540) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:400) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:219) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1459) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.query.internal.AbstractProducedQuery.doList(AbstractProducedQuery.java:1649) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1617) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] ... 11 more Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: An error occurred during the current command (Done status 0). Transaction (Process ID 76) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:237) ~[mssql-jdbc-11.2.2.jre11.jar:?] at com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer$FetchBufferTokenHandler.onDone(SQLServerResultSet.java:5396) ~[mssql-jdbc-11.2.2.jre11.jar:?] at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:99) ~[mssql-jdbc-11.2.2.jre11.jar:?] at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37) ~[mssql-jdbc-11.2.2.jre11.jar:?] at com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer.nextRow(SQLServerResultSet.java:5491) ~[mssql-jdbc-11.2.2.jre11.jar:?] at com.microsoft.sqlserver.jdbc.SQLServerResultSet.fetchBufferNext(SQLServerResultSet.java:1796) ~[mssql-jdbc-11.2.2.jre11.jar:?] at com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerResultSet.java:1054) ~[mssql-jdbc-11.2.2.jre11.jar:?] at org.hibernate.loader.Loader.getRowsFromResultSet(Loader.java:1043) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.processResultSet(Loader.java:998) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.doQuery(Loader.java:967) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:357) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.doList(Loader.java:2868) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.doList(Loader.java:2850) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2682) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.Loader.list(Loader.java:2677) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:540) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:400) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:219) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1459) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.query.internal.AbstractProducedQuery.doList(AbstractProducedQuery.java:1649) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1617) ~[hibernate-core-5.6.14.Final.jar:5.6.14.Final] ... 11 more{noformat} ( https://hibernate.atlassian.net/browse/HSEARCH-4774#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4774#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#100214- sha1:bdfa1eb )

2 years, 12 months