August 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-17050) JPA Criteria Queries using datediff and temporal units broken due to SqmDurationUnit cast

by Chris Popp (JIRA)

Chris Popp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmI3M2NjYzk0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-17050?atlOrigin=eyJpIjoiZmI3M2... ) HHH-17050 ( https://hibernate.atlassian.net/browse/HHH-17050?atlOrigin=eyJpIjoiZmI3M2... ) JPA Criteria Queries using datediff and temporal units broken due to SqmDurationUnit cast ( https://hibernate.atlassian.net/browse/HHH-17050?atlOrigin=eyJpIjoiZmI3M2... ) Change By: Chris Popp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I was trying to execute a JPA Criteria Query using Hibernate 6 calling the datediff function, but it seems that due to the cast to SqmDurationUnit in TimestampdiffFunction->TimestampdiffFunctionReturnTypeResolver I’m unable to supply a temporal unit that will be accepted. Given an entityManager the following demonstrates it when it throws an exception with the failed cast: {noformat}CriteriaBuilder cb = entityManager.getCriteriaBuilder(); Expression<Long> dateDiffFunc = cb.function("DATEDIFF", Long.class, criteriaBuilder cb.literal(TemporalUnit.MINUTE), criteriaBuilder cb.currentDate(), criteriaBuilder cb.currentDate()); CriteriaQuery<Long> cr = cb.createQuery(Long.class) .select(dateDiffFunc); entityManager.createQuery(cr).getResultList();{noformat} {quote}Caused by: java.lang.ClassCastException: class org.hibernate.query.sqm.tree.expression.SqmLiteral cannot be cast to class org.hibernate.query.sqm.tree.expression.SqmDurationUnit at org.hibernate.dialect.function.TimestampdiffFunction$TimestampdiffFunctionReturnTypeResolver.resolveFunctionReturnType(TimestampdiffFunction.java:133){quote} ( https://hibernate.atlassian.net/browse/HHH-17050#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-17050#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#100234- sha1:9e2db29 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17050) JPA Criteria Queries using datediff and temporal units broken due to SqmDurationUnit cast

by Chris Popp (JIRA)

Chris Popp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTcyOWFjOWRi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-17050?atlOrigin=eyJpIjoiNTcyOW... ) HHH-17050 ( https://hibernate.atlassian.net/browse/HHH-17050?atlOrigin=eyJpIjoiNTcyOW... ) JPA Criteria Queries using datediff and temporal units broken due to SqmDurationUnit cast ( https://hibernate.atlassian.net/browse/HHH-17050?atlOrigin=eyJpIjoiNTcyOW... ) Issue Type: Bug Affects Versions: 6.2.6 Assignee: Unassigned Created: 08/Aug/2023 13:28 PM Priority: Minor Reporter: Chris Popp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I was trying to execute a JPA Criteria Query using Hibernate 6 calling the datediff function, but it seems that due to the cast to SqmDurationUnit in TimestampdiffFunction->TimestampdiffFunctionReturnTypeResolver I’m unable to supply a temporal unit that will be accepted. Given an entityManager the following demonstrates it when it throws an exception with the failed cast: CriteriaBuilder cb = entityManager.getCriteriaBuilder(); Expression<Long> dateDiffFunc = cb.function("DATEDIFF", Long.class, criteriaBuilder.literal(TemporalUnit.MINUTE), criteriaBuilder.currentDate(), criteriaBuilder.currentDate()); CriteriaQuery<Long> cr = cb.createQuery(Long.class) .select(dateDiffFunc); entityManager.createQuery(cr).getResultList(); > > > > Caused by: java.lang.ClassCastException: class > org.hibernate.query.sqm.tree.expression.SqmLiteral cannot be cast to class > org.hibernate.query.sqm.tree.expression.SqmDurationUnit > at > org.hibernate.dialect.function.TimestampdiffFunction$TimestampdiffFunctionReturnTypeResolver.resolveFunctionReturnType(TimestampdiffFunction.java:133) > > > ( https://hibernate.atlassian.net/browse/HHH-17050#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-17050#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17049) Extra records created for entities created in constructor

by Rob Scala (JIRA)

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17049) Extra records created for entities created in constructor

by Rob Scala (JIRA)

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17049) Extra records created for entities created in constructor

by Rob Scala (JIRA)

Rob Scala ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiY2YwY2MyZjIw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-17049?atlOrigin=eyJpIjoiY2YwY2... ) HHH-17049 ( https://hibernate.atlassian.net/browse/HHH-17049?atlOrigin=eyJpIjoiY2YwY2... ) Extra records created for entities created in constructor ( https://hibernate.atlassian.net/browse/HHH-17049?atlOrigin=eyJpIjoiY2YwY2... ) Issue Type: Bug Affects Versions: 6.3.0.CR1 Assignee: Unassigned Components: hibernate-core Created: 08/Aug/2023 13:00 PM Environment: Hibernate 6.3.0.CR1 H2 database bytecode enhancement on Priority: Major Reporter: Rob Scala ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I have two cases where entities created in a constructor of another entity are persisted in the next transaction, even after the entity is replaced upon loading from the database. For example: @Entity public class Person { @Id @GeneratedValue(strategy= GenerationType.IDENTITY) private long id; @OneToOne(orphanRemoval = true , cascade = CascadeType.ALL, fetch = FetchType.LAZY) private ContactInfo contactInfo = new ContactInfo(); private String firstName; ... } In some conditions, when I load a Person object (entityManager.find), then set its firstName and commit the transaction, the firstName is changed, but an extra ContactInfo record is unexpectedly created. I expect the ContactInfo instance that was created in the constructor to be discarded when the Person entity is loaded with a ContactInfo record from the database. The database ends up with unreferenced records. This only happens for me when using bytecode enhancement. I have two test cases that reproduce this behavior. One involves a bi-directional OneToOne relationship. Here is the repo: git(a)github.com :robscala/extra_inserts_OneToOne_bi_test.git @Entity public class Person { @Id @GeneratedValue(strategy= GenerationType.IDENTITY) private long id; private String firstName; @OneToOne(orphanRemoval= true , cascade={CascadeType.PERSIST, CascadeType.REMOVE}, fetch=FetchType.LAZY) private LoginAccount loginAccount = new LoginAccount(); } @Entity public class LoginAccount { @Id @GeneratedValue(strategy= GenerationType.IDENTITY) private long id; private String name; @OneToOne(orphanRemoval= true , cascade= CascadeType.ALL, fetch= FetchType.LAZY) private AccountPreferences accountPreferences = new AccountPreferences(); @OneToOne(mappedBy = "loginAccount" ) private Person owner; } @Entity public class AccountPreferences { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private long id; private boolean open = false ; } In this case, after loading a Person and performing a transaction, an extra record in the AccountPreferences table is created. The other case involves a polymorphic class, Company. Here is the repo: git(a)github.com :robscala/extra_inserts_polymorphic_test.git @Entity public class Person { @Id @GeneratedValue(strategy= GenerationType.IDENTITY) private long id; private String firstName; @OneToOne(orphanRemoval = true , cascade = CascadeType.ALL, fetch = FetchType.LAZY) private ContactInfo contactInfo = new ContactInfo(); @ManyToOne(fetch=FetchType.LAZY, cascade = CascadeType.ALL) private Company company; } @Entity @Inheritance(strategy= InheritanceType.JOINED) @DiscriminatorColumn(name= "CompanyType" , discriminatorType= DiscriminatorType.INTEGER) public abstract class Company { @Id @GeneratedValue(strategy= GenerationType.IDENTITY) protected long id; @OneToOne(orphanRemoval= true , cascade=CascadeType.PERSIST, fetch=FetchType.LAZY) private ContactInfo contactInfo = new ContactInfo(); } @Entity @DiscriminatorValue( "9" ) public class CustomerCompany extends Company { private String zipCode; @ManyToOne(fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST, CascadeType.REMOVE}) private CustomerCompany parent; } In this case, after loading a Person and performing a transaction, an extra record in the ContactInfo table is created. ( https://hibernate.atlassian.net/browse/HHH-17049#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-17049#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-16577) Index Out of Bound Exception

by Falko Modler (JIRA)

Falko Modler ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiOThmOT... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiOThmOT... ) I’m seing the same exception in Quarkus 3.2.3 / Hibernate 6.2.7. Trying to gather more info… ( https://hibernate.atlassian.net/browse/HHH-16577#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16577#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-17040) Hibernate can return duplicate records on join depending on row ordering

by Alex Wood (JIRA)

Alex Wood ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTQzOWI1YTI3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-17040?atlOrigin=eyJpIjoiOTQzOW... ) HHH-17040 ( https://hibernate.atlassian.net/browse/HHH-17040?atlOrigin=eyJpIjoiOTQzOW... ) Hibernate can return duplicate records on join depending on row ordering ( https://hibernate.atlassian.net/browse/HHH-17040?atlOrigin=eyJpIjoiOTQzOW... ) Change By: Alex Wood ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) We have a query that is fetching a grandchild collection via outer join. There should only be one root object but in certain cases Hibernate can return duplicate root objects. The cause of the inconsistency seems to be the ordering of the rows in the results. If all the rows for the root object are grouped together (via an “order by” clause) for example, only one root is returned. If the rows are disordered, duplicates are returned. I’ve simulated the disordered results using an “order by random()” in the unit test, but in our product environment we’ve seen rows can be returned ordered or unordered (it seems to depend on the number of rows in the table as to whether the database decides to order the results). I’ve included explain plans for different database behavior for the same query as part of my pull request. Unit test is available at [https://github.com/hibernate/hibernate-test-case-templates/pull/301|https...] ( https://hibernate.atlassian.net/browse/HHH-17040#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-17040#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-16798) ClassCastException in Hibernate 6 when "join fetch" is used in a query with entity inheritance

by Seong Lee (JIRA)

Seong Lee ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-16798 ( https://hibernate.atlassian.net/browse/HHH-16798?atlOrigin=eyJpIjoiZjUwZD... ) Re: ClassCastException in Hibernate 6 when "join fetch" is used in a query with entity inheritance ( https://hibernate.atlassian.net/browse/HHH-16798?atlOrigin=eyJpIjoiZjUwZD... ) Hello, i’m also in a similar situation and it is not working on 6.2.6.Final or 6.3.0.CR1. Posted my case in a comment here: https://hibernate.atlassian.net/browse/HHH-16934?focusedCommentId=112562 ( https://hibernate.atlassian.net/browse/HHH-16798#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16798#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-15469) Missing EntityNotFoundException while using @ManyToOne / @OneToMany and EntityManager interface

by Peter Raupp (JIRA)

Peter Raupp ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=630c5e1... ) *commented* on HHH-15469 ( https://hibernate.atlassian.net/browse/HHH-15469?atlOrigin=eyJpIjoiODY1OT... ) Re: Missing EntityNotFoundException while using @ManyToOne / @OneToMany and EntityManager interface ( https://hibernate.atlassian.net/browse/HHH-15469?atlOrigin=eyJpIjoiODY1OT... ) @Christian Beikov > > > > According to the semantics of JPA, calling persist with a REMOVED entity > will result in the entity becoming managed again. > > I'm not questioning that approach at all. The only issue with this JIRA ticket is why an exception is thrown in one case and not in the other? When this occurs, I want to be notified about it, whether I'm using a Hibernate session or the EntityManager. It is disastrous that in one case an exception is thrown and in the other case not, even though it is the same semantics. This is simply a bad quality of the software. It is your decision to reopen the bug and thus improve the quality of the software. ( https://hibernate.atlassian.net/browse/HHH-15469#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15469#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

[JIRA] (HHH-16934) Fetching multiple fields of the same base class with InheritanceType.SINGLE_TABLE throws PropertyAccessException

by Seong Lee (JIRA)

Seong Lee ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-16934 ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiYTQ1M2... ) Re: Fetching multiple fields of the same base class with InheritanceType.SINGLE_TABLE throws PropertyAccessException ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiYTQ1M2... ) Hello, I am seeing this exact same error when using a InheritanceType.JOINED type on the parent. This was working fine on SpringBoot 3.0.6 I am on SpringBoot 3.1.2 , which uses Hibernate 6.2.6.Final. I’ve also tried forcing the 6.3.0.CR1 version and still see the error. This is written in Kotlin. @Entity @Table(name = "Resource") @Inheritance(strategy = InheritanceType.JOINED) @DiscriminatorColumn(name = "RESOURCE_TYPE_CD", discriminatorType = DiscriminatorType.INTEGER, columnDefinition = "INT") abstract class Resource( @Id @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "RESOURCE_ID_SEQ") @SequenceGenerator(name = "RESOURCE_ID_SEQ", sequenceName = "RESOURCE_ID_SEQ", allocationSize = 1) override var id: Long? = null, @Column(name = "RESOURCE_TYPE_CD", insertable = false, updatable = false) open var resourceType: ResourceType ): MutableAuditableBaseJpa<Long>() { ... } @Entity @Table(name = "RESOURCE_FUTURE_ROLE") @DiscriminatorValue("1") class FutureRole( ... ): Resource(null, ResourceType.FUTURE_ROLE) { ... } @Entity @Table(name = "RESOURCE_CURRENT_ROLE") @DiscriminatorValue("2") class CurrentRole( ... ): Resource(null, ResourceType.CURRENT_ROLE) { ... } @Entity @Table(name = "RECORD") open class Record( @Column(name = "RESOURCE_ID") override var resourceId: Long, ... ): MutableAuditableBaseJpa<Long>() { @OneToOne @NotFound(action = NotFoundAction.IGNORE) @JoinColumn(name = "RESOURCE_ID", insertable = false, updatable = false) open var futureRole: FutureRole? = null @OneToOne @NotFound(action = NotFoundAction.IGNORE) @JoinColumn(name = "RESOURCE_ID", insertable = false, updatable = false) open var employee: CurrentRole? = null } Caused by: org.hibernate.PropertyAccessException: Could not set value of type [com.hidden.CurrentRole]: 'com.hidden.Record.futureRole' (setter) at org.hibernate.property.access.spi.SetterFieldImpl.set(SetterFieldImpl.java:88) at org.hibernate.persister.entity.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:4360) at org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.initializeEntityInstance(AbstractEntityInitializer.java:837) at org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.initializeEntity(AbstractEntityInitializer.java:797) at org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.initializeInstance(AbstractEntityInitializer.java:783) at org.hibernate.sql.results.internal.InitializersList.initializeInstance(InitializersList.java:71) at org.hibernate.sql.results.internal.StandardRowReader.coordinateInitializers(StandardRowReader.java:109) at org.hibernate.sql.results.internal.StandardRowReader.readRow(StandardRowReader.java:86) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:201) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:33) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:361) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:168) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:93) at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:31) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.lambda$new$0(ConcreteSqmSelectQueryPlan.java:109) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:305) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:246) at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:509) at org.hibernate.query.spi.AbstractSelectionQuery.list(AbstractSelectionQuery.java:427) at org.hibernate.query.spi.AbstractSelectionQuery.getSingleResult(AbstractSelectionQuery.java:559) Note: I understand @DiscriminatorColumn is unnecessary for a Joined Inheritance, but this was existing logic I have yet to change. ( https://hibernate.atlassian.net/browse/HHH-16934#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16934#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#100233- sha1:7fb7fe8 )

1 year, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2023