January 2023 - hibernate-issues - Jboss List Archives

[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 )

1 year, 8 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 )

1 year, 8 months

1
0
0 / 0

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

by Marko Bekhta (JIRA)

1 year, 8 months

1
0
0 / 0

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

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

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

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

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

by Automation for Jira (JIRA)

1 year, 8 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 )

1 year, 8 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 )

1 year, 8 months

1
0
0 / 0

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

by pioneer.vvs＠gmail.com (JIRA)

1 year, 8 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)

1 year, 8 months

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 January 2023