May 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13235) Java exception when using @CreationTimestamp or @UpdateTimestamp annotation in Embeddable

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-11607) Transient doesn't work with MappedSuperclass values

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16555) Join fetch query in combination with the inheritance pattern not working in hibernate 6

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16569) Batch fetch leads to some collections to be wrongly initialized with empty due to wrong generated SQL

by Andrea Boriero (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16573) Embeddable element collection with updateable = false leads to NullPointerException

by Andrea Boriero (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16541) (Jakarta EE 10 Platform TCK) jpa/core/lock/query/Client.java#getResultListTest1 test regression

by Martin Marciano (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4574) Explicit binding of constructor parameters for @ProjectionConstructor

by Automation for Jira (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16578) Incorrect validation error for tinyint, but and datetime

by Jan Schatteman (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16578) Incorrect validation error for tinyint, but and datetime

by Max (JIRA)

Max ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-16578 ( https://hibernate.atlassian.net/browse/HHH-16578?atlOrigin=eyJpIjoiOWI5Zj... ) Re: Incorrect validation error for tinyint, but and datetime ( https://hibernate.atlassian.net/browse/HHH-16578?atlOrigin=eyJpIjoiOWI5Zj... ) I’m not sure I’m following, sorry. Java int: -2,147,483,648 to 2,147,483,647 MySQL tinyint (no exception thrown): -128 to 128 MySQL tinyint unsigned (exception thrown): 0 to 255 The problem is that @Column(name = "level", columnDefinition = "tinyint") ` is ok, but for some reason @Column(name = "level", columnDefinition = "tinyint unsigned") ` is not, although it’s closer to the actual database table definition. Or do you mean negative values here somehow make a difference? What about positive values over 128 in case of tinyint? ( https://hibernate.atlassian.net/browse/HHH-16578#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16578#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16111) Field annotated with @Version does not increase when entity is updated using merge

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15726) Disjunction with treat results in too restrictive query

by Christian Beikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Incorrect enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiMjUzMj... ) Re: Incorrect enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiMjUzMj... ) Is there a good spot in EnhancerImpl (or PersistentAttributeTransformer ) where it is know that a field is read or written from particular methods? There is ByteBuddyEnhancementContext#resolveGetter but that is actually part of the problem (it simply looks for methods based on the field name). ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16505) Interpretation of "bare" left-join alias reference in HQL

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16505) Interpretation of "bare" left-join alias reference in HQL

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16517) H6: Problems with flush when batch is ON (without @DynamicUpdate)

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16517) H6: Problems with flush when batch is ON (without @DynamicUpdate)

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16589) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000

by Adrodoc (JIRA)

Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmJkM2M3YWU2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiZmJkM2... ) HHH-16589 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiZmJkM2... ) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiZmJkM2... ) Change By: Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) If you enable {{hibernate.query.in_clause_parameter_padding}} in {{persistence.xml}}and then execute the following query with 1900 parameters: {{select m from MyEntity m where m.id in ?1}} You will get this error {{ORA-01795: maximum number of expressions in a list is 1000}}. The issue lies in {{AbstractSqlAstTranslator}}: if there are more {{listExpressions}} than {{inExprLimit}} and {{inClauseParameterPaddingEnabled}} is true then {{bindValueMaxCount}} is calculated as {{ceilingPowerOfTwo( bindValueCount % inExprLimit )}}. In our example this is {{ceilingPowerOfTwo(1900 % 1000) == 1024}}. This result is then used to pad the last in clause without checking {{inExprLimit}} again: [https://github.com/hibernate/hibernate-orm/blob/6746c30275b6600622d82613d...] {code:java} if ( inClauseParameterPaddingEnabled ) { final Expression lastExpression = itemAccessor.apply( listExpressions.get( listExpressions.size() - 1 ) ); for ( ; ` itemNumber < bindValueMaxCount ; itemNumber++ ) { appendSql( separator ); lastExpression.accept( this ); separator = COMA_SEPARATOR; } }{code} A simple fix would be to change the condition of this for-loop to {{itemNumber < Math.min(bindValueMaxCount, inExprLimit)}}, but I feel like the whole calculation could be simplified. I added a testcase that reproduces the issue, but I don’t know how to write an assertion that would fail the test when there is an in clause with more than 1000 parameters. So the test always passes, but you can see the incorrectly generated SQL in the log: [https://github.com/Adrodoc/HHH-16589/commit/581cf4077622ce448b482859eb909...] ( https://hibernate.atlassian.net/browse/HHH-16589#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16589#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16576) problem in query involving union on MariaDB and Oracle

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16576 ( https://hibernate.atlassian.net/browse/HHH-16576?atlOrigin=eyJpIjoiM2VjMj... ) Re: problem in query involving union on MariaDB and Oracle ( https://hibernate.atlassian.net/browse/HHH-16576?atlOrigin=eyJpIjoiM2VjMj... ) Noticed this test ( FunctionTests#testMaxOverUnion ) also fails on MySQL 5.7 on our nightly CI pipeline ( https://ci.hibernate.org/job/hibernate-orm-nightly/job/main/194/testRepor... ) , probably for the same reason it fails on MariaDB. ( https://hibernate.atlassian.net/browse/HHH-16576#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16576#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4853) On JDK 21-ea+21, projection constructor relying on cannical record constructor result in all-null records

by Automation for Jira (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4826) Remove unused Maven plugins from the POM

by Automation for Jira (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-11607) Transient doesn't work with MappedSuperclass values

by Martin Marciano (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-13235) Java exception when using @CreationTimestamp or @UpdateTimestamp annotation in Embeddable

by Martin Marciano (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4853) On JDK 21-ea+21, projection constructor relying on cannical record constructor result in all-null records

by Yoann Rodière (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4853) On JDK 21-ea+21, projection constructor relying on cannical record constructor result in all-null records

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiNTMzMDVi... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-4853?atlOrigin=eyJpIjoiNTM... ) HSEARCH-4853 ( https://hibernate.atlassian.net/browse/HSEARCH-4853?atlOrigin=eyJpIjoiNTM... ) On JDK 21-ea+21, projection constructor relying on cannical record constructor result in all-null records ( https://hibernate.atlassian.net/browse/HSEARCH-4853?atlOrigin=eyJpIjoiNTM... ) Issue Type: Bug Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: mapper-pojo-base Created: 11/May/2023 05:08 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) It seems parameters of record canonical constructors are considired implicit ( Parameter#isImplicit returns true ) starting with JDK 21-ea+21, which causes this check ( https://github.com/hibernate/hibernate-search/blob/6c6a2c6f27b0087fdbd884... ) to incorrectly assume these constructor parameters are for the surrounding instance in nested classes, leading to all parameters being set to null when projecting. See also: https://ci.hibernate.org/job/hibernate-search/job/main/666/ 14:09:20,303 (main) DEBUG PojoSearchQueryElementRegistryBuilder:89 - HSEARCH700117: Constructor projection for type 'org.hibernate.search.integrationtest.mapper.pojo.mapping.definition.ProjectionConstructorRecordIT$2MyProjection': valueCreateHandle: MethodHandleValueCreateHandle[public org.hibernate.search.integrationtest.mapper.pojo.mapping.definition.ProjectionConstructorRecordIT$2MyProjection(java.lang.String,java.lang.Integer)] innerDefinitions: - <null projection> - <null projection> ( https://hibernate.atlassian.net/browse/HSEARCH-4853#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4853#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16589) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000

by Adrodoc (JIRA)

Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWMyNTQ1ODYx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiNWMyNT... ) HHH-16589 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiNWMyNT... ) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiNWMyNT... ) Change By: Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) If you enable {{hibernate.query.in_clause_parameter_padding}} in {{persistence.xml}}and then execute the following query with 1900 parameters: {{select m from MyEntity m where m.id in ?1}} You will get this error {{ORA-01795: maximum number of expressions in a list is 1000}}. The issue lies in {{AbstractSqlAstTranslator}}: if there are more {{listExpressions}} than {{inExprLimit}} and {{inClauseParameterPaddingEnabled}} is true then {{bindValueMaxCount}} is calculated as {{ceilingPowerOfTwo( bindValueCount % inExprLimit )}}. In our example this is {{ceilingPowerOfTwo(1900 % 1000) == 1024}}. This result is then used to pad the last in clause without checking {{inExprLimit}} again: [https://github.com/hibernate/hibernate-orm/blob/6746c30275b6600622d82613d...] {code:java} if ( inClauseParameterPaddingEnabled ) { final Expression lastExpression = itemAccessor.apply( listExpressions.get( listExpressions.size() - 1 ) ); for ( ; `; itemNumber++ ) { appendSql( separator ); lastExpression.accept( this ); separator = COMA_SEPARATOR; } }{code} A simple fix would be to change the condition of this for-loop to {{itemNumber < Math.min(bindValueMaxCount, inExprLimit)}}, but I feel like the whole calculation could be simplified. I added a testcase that reproduces the issue, but I don’t know how to write an assertion that would fail the test when there is an in clause with more than 1000 parameters. So the test always passes, but you can see the incorrectly generated SQL in the log: [https://github.com/Adrodoc/HHH-16589/commit/581cf4077622ce448b482859eb909...] ( https://hibernate.atlassian.net/browse/HHH-16589#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16589#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16589) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000

by Adrodoc (JIRA)

Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOGJhNmIyODRi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiOGJhNm... ) HHH-16589 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiOGJhNm... ) In-Clause Parameter Padding mistreats Dilect.getInExpressionCountLimit which can cause ORA-01795: maximum number of expressions in a list is 1000 ( https://hibernate.atlassian.net/browse/HHH-16589?atlOrigin=eyJpIjoiOGJhNm... ) Issue Type: Bug Affects Versions: 6.2.1, 6.2.2 Assignee: Unassigned Created: 11/May/2023 04:55 AM Priority: Major Reporter: Adrodoc ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b2a4a0... ) If you enable hibernate.query.in_clause_parameter_padding in {{persistence.xml}}and then execute the following query with 1900 parameters: select m from MyEntity m where m.id in ?1 You will get this error ORA-01795: maximum number of expressions in a list is 1000. The issue lies in AbstractSqlAstTranslator : if there are more listExpressions than inExprLimit and inClauseParameterPaddingEnabled is true then bindValueMaxCount is calculated as ceilingPowerOfTwo( bindValueCount % inExprLimit ). In our example this is ceilingPowerOfTwo(1900 % 1000) == 1024. This result is then used to pad the last in clause without checking inExprLimit again: https://github.com/hibernate/hibernate-orm/blob/6746c30275b6600622d82613d... if ( inClauseParameterPaddingEnabled ) { final Expression lastExpression = itemAccessor.apply( listExpressions.get( listExpressions.size() - 1 ) ); for ( ; `; itemNumber++ ) { appendSql( separator ); lastExpression.accept( this ); separator = COMA_SEPARATOR; } } A simple fix would be to change the condition of this for-loop to itemNumber < Math.min(bindValueMaxCount, inExprLimit) , but I feel like the whole calculation could be simplified. ( https://hibernate.atlassian.net/browse/HHH-16589#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16589#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16588) getResultStream() together with join fetch delivers wrong results

by Adrian Pauli (JIRA)

Adrian Pauli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5eda31c... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNzg4OTQ1ZmQy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16588?atlOrigin=eyJpIjoiNzg4OT... ) HHH-16588 ( https://hibernate.atlassian.net/browse/HHH-16588?atlOrigin=eyJpIjoiNzg4OT... ) getResultStream() together with join fetch delivers wrong results ( https://hibernate.atlassian.net/browse/HHH-16588?atlOrigin=eyJpIjoiNzg4OT... ) Issue Type: Bug Affects Versions: 6.2.1 Assignee: Unassigned Created: 11/May/2023 04:50 AM Environment: Quarkus 3.0.2 together with hibernate 6.2.1 Priority: Major Reporter: Adrian Pauli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5eda31c... ) Using “join fetch” together with getResultStream delivers incomplete entities (multiplie times) depending on the order of the db result rows. *How to reproduce* ------------------ *Setup:* Entites: @Getter @Setter @Entity @Table(name = "notification_list" ) @ToString public class NotificationListEntity { @Id @Column(name = "id" ) private UUID id; @Column(name = "name" ) private String name; @OneToMany(mappedBy = "notificationList" ) private Set<RoomEntity> roomIds; } @Getter @Setter @Entity @Table(name = "notification_list_room" ) @ToString public class RoomEntity { @Id @Column(name = "room_id" ) UUID roomId; @ManyToOne @JoinColumn(name = "notification_list_id" ) @ToString.Exclude NotificationListEntity notificationList; } Prefill the db with: insert into notification_list (id, name ) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , ' A ' ); insert into notification_list (id, name ) values ( 'd5d3bbcc-1c00-4aa5-af80-4ecd2aedfb99' , 'B' ); insert into notification_list (id, name ) values ( '73af7a07-1a6b-4f65-b77f-ab1613e7849d' , ' C ' ); insert into notification_list_room (notification_list_id, room_id) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , '8f2890bb-79ef-4b09-9f04-1d1a2024cfe1' ); insert into notification_list_room (notification_list_id, room_id) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , 'ec7f587d-13c7-4f1f-105d-312ee5d655e8' ); insert into notification_list_room (notification_list_id, room_id) values ( 'd5d3bbcc-1c00-4aa5-af80-4ecd2aedfb99' , '31197476-222e-47ef-87e2-4f0fefb0b97a' ); insert into notification_list_room (notification_list_id, room_id) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , '92b12b36-8c00-4951-10db-263facfcb214' ); insert into notification_list_room (notification_list_id, room_id) values ( '73af7a07-1a6b-4f65-b77f-ab1613e7849d' , 'd3acc6a1-e223-421d-a135-4142f159d548' ); insert into notification_list_room (notification_list_id, room_id) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , 'b0b12a45-0e1b-4b0d-9fb1-fab948835605' ); insert into notification_list_room (notification_list_id, room_id) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , '8be1d3b3-2f1d-48b2-9982-77814003ce97' ); insert into notification_list_room (notification_list_id, room_id) values ( '99006f27-a59f-491f-b7f8-7e83b8fc02b0' , 'df2ba159-92b5-4e78-1008-b181e5406a91' ); Methods: public List<NotificationListEntity> streamAll() { return entityManager .createQuery( """ SELECT nle FROM NotificationListEntity nle JOIN fetch nle.roomIds """, NotificationListEntity.class) .getResultStream(); } public List<NotificationListEntity> listAll() { return entityManager .createQuery( """ SELECT nle FROM NotificationListEntity nle JOIN fetch nle.roomIds """, NotificationListEntity.class) .getResultList(); } *Result:* Calling the “listAll()” delivers correct entities: NotificationListEntity(id=99006f27-a59f-491f-b7f8-7e83b8fc02b0, name=A, roomIds=[RoomEntity(roomId=b0b12a45-0e1b-4b0d-9fb1-fab948835605), RoomEntity(roomId=df2ba159-92b5-4e78-1008-b181e5406a91), RoomEntity(roomId=8be1d3b3-2f1d-48b2-9982-77814003ce97), RoomEntity(roomId=ec7f587d-13c7-4f1f-105d-312ee5d655e8), RoomEntity(roomId=8f2890bb-79ef-4b09-9f04-1d1a2024cfe1), RoomEntity(roomId=92b12b36-8c00-4951-10db-263facfcb214)]) NotificationListEntity(id=d5d3bbcc-1c00-4aa5-af80-4ecd2aedfb99, name=B, roomIds=[RoomEntity(roomId=31197476-222e-47ef-87e2-4f0fefb0b97a)]) NotificationListEntity(id=73af7a07-1a6b-4f65-b77f-ab1613e7849d, name=C, roomIds=[RoomEntity(roomId=d3acc6a1-e223-421d-a135-4142f159d548)]) Calling the “streamAll()” delivers wrong entities: NotificationListEntity(id=99006f27-a59f-491f-b7f8-7e83b8fc02b0, name=A, roomIds=[RoomEntity(roomId=8f2890bb-79ef-4b09-9f04-1d1a2024cfe1), RoomEntity(roomId=ec7f587d-13c7-4f1f-105d-312ee5d655e8)]) NotificationListEntity(id=d5d3bbcc-1c00-4aa5-af80-4ecd2aedfb99, name=B, roomIds=[RoomEntity(roomId=31197476-222e-47ef-87e2-4f0fefb0b97a)]) NotificationListEntity(id=99006f27-a59f-491f-b7f8-7e83b8fc02b0, name=A, roomIds=[RoomEntity(roomId=8f2890bb-79ef-4b09-9f04-1d1a2024cfe1), RoomEntity(roomId=ec7f587d-13c7-4f1f-105d-312ee5d655e8)]) NotificationListEntity(id=73af7a07-1a6b-4f65-b77f-ab1613e7849d, name=C, roomIds=[RoomEntity(roomId=d3acc6a1-e223-421d-a135-4142f159d548)]) NotificationListEntity(id=99006f27-a59f-491f-b7f8-7e83b8fc02b0, name=A, roomIds=[RoomEntity(roomId=8f2890bb-79ef-4b09-9f04-1d1a2024cfe1), RoomEntity(roomId=ec7f587d-13c7-4f1f-105d-312ee5d655e8)]) When adding a “order by nle.id ( http://nle.id ) ” it also works correctly with the steam. So the getResultStream should somehow handle this correctly or warn that fetch is not allowed. ( https://hibernate.atlassian.net/browse/HHH-16588#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16588#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16587) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field :

by Martin Panzer (JIRA)

Martin Panzer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed8c2e... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTM1Y2M2MzE4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiNTM1Y2... ) HHH-16587 ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiNTM1Y2... ) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field : ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiNTM1Y2... ) Change By: Martin Panzer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed8c2e... ) h3. Describe the bug I have the following field in my entity: {noformat}[...] public class Rule { [...] @JdbcTypeCode(SqlTypes.JSON) @Column(name = "condition", columnDefinition = "json") private Predicate condition; [..] }{noformat} During quarkus startup I now get following warning: {noformat}2023-05-05 11:36:39,583 WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field : com.activelogistics.wolf.webruleservice.rule.db.model.Rule_#condition; this may or may not indicate a problem with the static metamodel {noformat} The metamodel is generated by following dependency: {noformat} <dependency> <groupId>org.hibernate.orm</groupId> <artifactId>hibernate-jpamodelgen</artifactId> <scope>provided</scope> </dependency>{noformat} The field condition is indeed missing in the metamodel. During the Q3 migration, I changed the field from this: {noformat} @Type(type = "io.hypersistence.utils.hibernate.type.json.JsonNodeBinaryType") @Column(name = "condition", columnDefinition = "json") private Predicate condition;{noformat} And the condition was included in the metamodel. Could it be, that {{JdbcTypeCode}} is not respected by the metamodel generator and therefore the field not included? h3. Expected behavior _No response_ h3. Actual behavior _No response_ h3. How to Reproduce? Reproducer: see attachment [orm-warning-json.zip|https://github.com/quarkusio/quarkus/files/11406031/...] # mvn clean compile quarkus:dev install # Warning is printed Now run the unit test {{JPAUnitTestCase}} # 2023-05-11 13:29:09 WARN MetadataContext:711 - HHH015011: Unable to locate static metamodel field : org.hibernate.bugs.MyEntity_#condition; this may or may not indicate a problem with the static metamodel h3. Output of {{uname -a}} or {{ver}} MINGW64_NT-10.0-19045 NANBCHL9NG3 3.3.6-341.x86_64 2022-09-05 20:28 UTC x86_64 Msys h3. Output of {{java -version}} openjdk version "17.0.4" 2022-07-19 OpenJDK Runtime Environment Temurin-17.0.4+8 (build 17.0.4+8) OpenJDK 64-Bit Server VM Temurin-17.0.4+8 (build 17.0.4+8, mixed mode, sharing) h3. GraalVM version (if different from Java) _No response_ h3. Quarkus version or git rev 3.0.2.Final h3. Build tool (ie. output of {{mvnw --version}} or {{gradlew --version}}) Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: C:\eclipse\tools\java\maven Java version: 17.0.4, vendor: Eclipse Adoptium, runtime: C:\eclipse\tools\java\17 Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" h3. Additional information _No response_ ( https://hibernate.atlassian.net/browse/HHH-16587#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16587#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16587) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field :

by Martin Panzer (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16587) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field :

by Martin Panzer (JIRA)

Martin Panzer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed8c2e... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTU5MzViOWFk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiNTU5Mz... ) HHH-16587 ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiNTU5Mz... ) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field : ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiNTU5Mz... ) Change By: Martin Panzer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed8c2e... ) h3. Describe the bug I have the following field in my entity: {noformat}[...] public class Rule { [...] @JdbcTypeCode(SqlTypes.JSON) @Column(name = "condition", columnDefinition = "json") private Predicate condition; [..] }{noformat} During quarkus startup I now get following warning: {noformat}2023-05-05 11:36:39,583 WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field : com.activelogistics.wolf.webruleservice.rule.db.model.Rule_#condition; this may or may not indicate a problem with the static metamodel {noformat} The metamodel is generated by following dependency: {noformat} <dependency> <groupId>org.hibernate.orm</groupId> <artifactId>hibernate-jpamodelgen</artifactId> <scope>provided</scope> </dependency>{noformat} The field condition is indeed missing in the metamodel. During the Q3 migration, I changed the field from this: {noformat} @Type(type = "io.hypersistence.utils.hibernate.type.json.JsonNodeBinaryType") @Column(name = "condition", columnDefinition = "json") private Predicate condition;{noformat} And the condition was included in the metamodel. Could it be, that {{JdbcTypeCode}} is not respected by the metamodel generator and therefore the field not included? h3. Expected behavior _No response_ h3. Actual behavior _No response_ h3. How to Reproduce? Reproducer: [orm-warning-json.zip|https://github.com/quarkusio/quarkus/files/11406031/...] # mvn clean compile quarkus:dev # Warning is printed h3. Output of {{uname -a}} or {{ver}} MINGW64_NT-10.0-19045 NANBCHL9NG3 3.3.6-341.x86_64 2022-09-05 20:28 UTC x86_64 Msys h3. Output of {{java -version}} openjdk version "17.0.4" 2022-07-19 OpenJDK Runtime Environment Temurin-17.0.4+8 (build 17.0.4+8) OpenJDK 64-Bit Server VM Temurin-17.0.4+8 (build 17.0.4+8, mixed mode, sharing) h3. GraalVM version (if different from Java) _No response_ h3. Quarkus version or git rev 3.0.2.Final h3. Build tool (ie. output of {{mvnw --version}} or {{gradlew --version}}) Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: C:\eclipse\tools\java\maven Java version: 17.0.4, vendor: Eclipse Adoptium, runtime: C:\eclipse\tools\java\17 Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" h3. Additional information _No response_ ( https://hibernate.atlassian.net/browse/HHH-16587#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16587#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16587) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field :

by Martin Panzer (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16578) Incorrect validation error for tinyint, but and datetime

by Čedomir Igaly (JIRA)

Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16578 ( https://hibernate.atlassian.net/browse/HHH-16578?atlOrigin=eyJpIjoiNWU1OD... ) Re: Incorrect validation error for tinyint, but and datetime ( https://hibernate.atlassian.net/browse/HHH-16578?atlOrigin=eyJpIjoiNWU1OD... ) Reason for the exception is because your property ‘level’ is declared as int and equivalent column type is tynint while column type for Java int (or Integer) should be integer. Column type tinyint is too short to accept larger integre values. If you change type of property level to Java byte, validation will work pass. ( https://hibernate.atlassian.net/browse/HHH-16578#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16578#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16555) Join fetch query in combination with the inheritance pattern not working in hibernate 6

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16586) Entity PUT via REST with all null payload fields is not updated in DB

by Matthieu Rickly (JIRA)

Matthieu Rickly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzI0YWMxNGIy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16586?atlOrigin=eyJpIjoiMzI0YW... ) HHH-16586 ( https://hibernate.atlassian.net/browse/HHH-16586?atlOrigin=eyJpIjoiMzI0YW... ) Entity PUT via REST with all null payload fields is not updated in DB ( https://hibernate.atlassian.net/browse/HHH-16586?atlOrigin=eyJpIjoiMzI0YW... ) Change By: Matthieu Rickly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When an Entity is passed with all null payload fields in a PUT REST resource, the entity is not marked as dirty, because the fields of the passed entity are compared with the (null) fields of a new entity. When the entity is merged into the context, I would expect the dirty marking to be performed between the passed entity and the entity from the persistence context (stored in the database), but no such thing occurs. Hence no update is scheduled for the entity and the database entity is unchanged. Entity: {noformat}public class Item implements Serializable { public static final String TABLE_NAME = "T_ITEM"; public static final String COLUMN_ID = "C_ID"; public static final String COLUMN_UUID = "C_UUID"; public static final String COLUMN_NAME = "C_NAME"; public static final String COLUMN_VERSION = "C_VERSION"; private static final long serialVersionUID = 1L; @Id @GeneratedValue @Column(name = COLUMN_ID) private Long id; @Column(name = COLUMN_UUID, length = 36) @Type(type = "org.hibernate.type.UUIDCharType") @DDLComment(value = "Application Assigned Primary Key", type = "UUID") private UUID uuid = UUID.randomUUID(); @Column(name = COLUMN_NAME, length = 10) @DDLComment("Name of Item") @Size(max = 10) private String name; @Version @Column(name = COLUMN_VERSION) @DDLComment("Optimistic Locking field") private Long version; protected Item() { } public Long getId() { return id; } public void setId(Long id) { this.id = id; } public UUID getUuid() { return uuid; } public String getName() { return name; } public Long getVersion() { return version; } /** * {@inheritDoc} * <p>Only {@code id} and {@code name} are considered.</p> */ @Override public boolean equals(Object o) { if (this == o) { return true; } if (o == null || getClass() != o.getClass()) { return false; } Item that = (Item) o; return Objects.equals(id, that.id) && Objects.equals(name, that.name); } /** * {@inheritDoc} * <p>Only {@code id} and {@code name} are considered.</p> */ @Override public int hashCode() { return Objects.hash(id, name); } @Override public String toString() { return "Item{id='" + id + '\'' + ", name='" + name + '\'' + '}'; } public static final class Builder { private Item entity = new Item(); public Builder() { } public Builder(final Item item) { this.entity = item; } public Builder name(final String name) { entity.name = name; return this; } public Item build() { Item result = this.entity; this.entity = null; return result; } } } {noformat} PUT REST Resource: {noformat} @PUT @Path("/{id}") @Consumes(MediaType.APPLICATION_JSON) public Response update(@PathParam("id") Long id, @Parameter(description = "Item", required = true) Item item) { Item updated = em.merge(item); return Response.ok(updated).build(); }{noformat} Test: {noformat} @Test void shouldUpdateItem() { String url = given(defaultSpec()) .when() .contentType("application/json") .body("{\"name\":\"bar\"}") .post(PATH) .then().extract().header("Location"); JsonPath jsonPath = given(defaultSpec()) .when() .contentType("application/json") .get(PATH + "/" + url.substring(url.lastIndexOf("/") + 1)).then() .statusCode(OK.getStatusCode()).extract().body().jsonPath(); Long id = jsonPath.getLong("id"); String nameAfterPost = jsonPath.getString("name"); Long version = jsonPath.getLong("version"); assertEquals("bar", nameAfterPost); String body = "{\"id\":" + id + ", \"uuid\":null, \"name\":null}"; given(defaultSpec()) .when() .contentType("application/json") .body(body) .put(PATH + "/" + id) .then() .statusCode(OK.getStatusCode()).extract().body().asString(); String nameAfterUpdate = given(defaultSpec()) .when() .contentType("application/json") .get(PATH + "/" + id) .then() .statusCode(OK.getStatusCode()).extract().body().jsonPath().getString("name"); assertEquals("bar", nameAfterUpdate); }{noformat} The final assert in the test shows that the entity has not been updated in the database. ( https://hibernate.atlassian.net/browse/HHH-16586#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16586#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16586) Entity PUT via REST with all null payload fields is not updated in DB

by Matthieu Rickly (JIRA)

Matthieu Rickly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWE5MTkzNDAx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16586?atlOrigin=eyJpIjoiNWE5MT... ) HHH-16586 ( https://hibernate.atlassian.net/browse/HHH-16586?atlOrigin=eyJpIjoiNWE5MT... ) Entity PUT via REST with all null payload fields is not updated in DB ( https://hibernate.atlassian.net/browse/HHH-16586?atlOrigin=eyJpIjoiNWE5MT... ) Change By: Matthieu Rickly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When an Entity is passed with all null payload fields in a PUT REST resource, the entity is not marked as dirty, because the fields of the passed entity are compared with the (null) fields of a new entity. When the entity is merged into the context, I would expect the dirty marking to be performed between the passed entity and the entity from the persistence context (stored in the database), but no such thing occurs. Hence no update is scheduled for the entity and the database entity is unchanged. ( https://hibernate.atlassian.net/browse/HHH-16586#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16586#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *commented* on HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiZDZhZj... ) Re: in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiZDZhZj... ) forum link: https://discourse.hibernate.org/t/hibernate-6-2-and-filterdefs-name-uniqu... ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16586) Entity PUT via REST with all null payload fields is not updated in DB

by Matthieu Rickly (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16585) In hibernate 6 a EnumType is returned as an ordinal instead of the actual enum type

by Maurice (JIRA)

Maurice ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b0057d... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjZhZGQ5ZDRj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16585?atlOrigin=eyJpIjoiMjZhZG... ) HHH-16585 ( https://hibernate.atlassian.net/browse/HHH-16585?atlOrigin=eyJpIjoiMjZhZG... ) In hibernate 6 a EnumType is returned as an ordinal instead of the actual enum type ( https://hibernate.atlassian.net/browse/HHH-16585?atlOrigin=eyJpIjoiMjZhZG... ) Issue Type: Bug Assignee: Unassigned Created: 11/May/2023 03:03 AM Environment: java 17 spring 6 windows 11 Priority: Major Reporter: Maurice ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b0057d... ) I have this @Query annotation @Query("SELECT new DTOs.EntityDTOs.cropvariety.CropVarietyPropagationDetailsDTO(s.cropVariety.id, cast(s.propagationMethod as Enums.PropagationMethod), s.daysUntilHarvestLongestEstimate, s.minimumTemperature, s.sowDepth) FROM CropVarietyPropagationDetails s WHERE s.cropVariety.id IN :idList") If i don’t explicitly cast s.propagationMethod as Enums.PropagationMethod the following error is thrown when calling the constructor CropVarietyPropagationDetailsDTO : java.lang.IllegalStateException: Could not determine appropriate instantiation strategy - no matching constructor found and one or more arguments did not define alias for bean-injection This is because s.propagationMethod is stored as an ordinal enum value in the database. However in Hibernate 5 this caused no issues. It would automatically convert the ordinal value to the corresponding Enum type value before injecting it into CropVarietyPropagationDetailsDTO. So i assume the current behavior can be considered a bug. Since hibernate 6 i also can’t use the ordinal value in a @Query jpql query statement anymore. The following no longer works: @Query("UPDATE User u SET u.userStatus = 0 WHERE u.userStatus = 1") Instead i have to define it like this: @Query("UPDATE User u SET u.userStatus = Enums.UserStatus.OFFLINE WHERE u.userStatus = Enums.UserStatus.ONLINE") ( https://hibernate.atlassian.net/browse/HHH-16585#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16585#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *commented* on HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiMWExMm... ) Re: in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiMWExMm... ) added a PR https://github.com/hibernate/hibernate-test-case-templates/pull/266 ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *commented* on HHH-16582 ( https://hibernate.atlassian.net/browse/HHH-16582?atlOrigin=eyJpIjoiMWMxND... ) Re: Alias XXX used for multiple from-clause elements error when executing query with 2 level join ( https://hibernate.atlassian.net/browse/HHH-16582?atlOrigin=eyJpIjoiMWMxND... ) Added a PR https://github.com/hibernate/hibernate-test-case-templates/pull/265 ( https://hibernate.atlassian.net/browse/HHH-16582#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16582#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16582 ( https://hibernate.atlassian.net/browse/HHH-16582?atlOrigin=eyJpIjoiMTViZj... ) Re: Alias XXX used for multiple from-clause elements error when executing query with 2 level join ( https://hibernate.atlassian.net/browse/HHH-16582?atlOrigin=eyJpIjoiMTViZj... ) Original post: https://discourse.hibernate.org/t/error-when-executing-query-with-multipl.... ( https://hibernate.atlassian.net/browse/HHH-16582#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16582#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *commented* on HHH-16582 ( https://hibernate.atlassian.net/browse/HHH-16582?atlOrigin=eyJpIjoiYWE4Ym... ) Re: Alias XXX used for multiple from-clause elements error when executing query with 2 level join ( https://hibernate.atlassian.net/browse/HHH-16582?atlOrigin=eyJpIjoiYWE4Ym... ) attached project with test case. Seems this is happening when you use interfaces. Without interfaces works fine ( https://hibernate.atlassian.net/browse/HHH-16582#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16582#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16464) Foreign key constraint not created for @OneToOne mapping with missing @MapsId

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16464 ( https://hibernate.atlassian.net/browse/HHH-16464?atlOrigin=eyJpIjoiN2EwMW... ) Re: Foreign key constraint not created for @OneToOne mapping with missing @MapsId ( https://hibernate.atlassian.net/browse/HHH-16464?atlOrigin=eyJpIjoiN2EwMW... ) (Note that an alternative resolution to this bug would be to reject the mapping, and ask the user to add a @MapsId annotation.) ( https://hibernate.atlassian.net/browse/HHH-16464#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16464#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16584) @JoinTable @ManyToOne should have a unique constraint on association table

by Gavin King (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16584) @JoinTable @ManyToOne should have a unique constraint on association tab;e

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmY4Y2IxMDU1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16584?atlOrigin=eyJpIjoiZmY4Y2... ) HHH-16584 ( https://hibernate.atlassian.net/browse/HHH-16584?atlOrigin=eyJpIjoiZmY4Y2... ) @JoinTable @ManyToOne should have a unique constraint on association tab;e ( https://hibernate.atlassian.net/browse/HHH-16584?atlOrigin=eyJpIjoiZmY4Y2... ) Issue Type: Bug Assignee: Unassigned Components: hibernate-core Created: 11/May/2023 01:32 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) A mapping like this: static class Book { @Id @GeneratedValue long id; @ManyToOne @JoinTable(name= "BOOKPUBLISHER" ) Publisher publisher; } Results in this DDL: create table BOOKPUBLISHER ( publisher_id bigint , id bigint not null , primary key (id) ) But the id column should have a unique constraint. The same issue occurs for @OneToOne , where both columns should have unique constraints, but only one unique constraint is added. ( https://hibernate.atlassian.net/browse/HHH-16584#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16584#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

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

by Prashant Guleria (JIRA)

Prashant Guleria ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYjY1OD... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYjY1OD... ) Hi, Tested with 6.2.2.Final and it seems the issue is not present in this version. However, I suggest to make this change: if (writtenValues != null ) { for ( String writtenFieldName: writtenFieldNames) { int attributeIndex = entityPersister.getEntityMetamodel().getPropertyIndex(writtenFieldName); if (attributeIndex >= 0) { entityPersister.setPropertyValue(target, attributeIndex, writtenValues[attributeIndex]); } } writtenFieldNames.clear(); } ( 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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *commented* on HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiOWNlY2... ) Re: in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiOWNlY2... ) attached test case ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16583) @JoinTable @ManyToOne blows up if no table name is explicitly specified

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjNiM2JiZTE4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16583?atlOrigin=eyJpIjoiZjNiM2... ) HHH-16583 ( https://hibernate.atlassian.net/browse/HHH-16583?atlOrigin=eyJpIjoiZjNiM2... ) @JoinTable @ManyToOne blows up if no table name is explicitly specified ( https://hibernate.atlassian.net/browse/HHH-16583?atlOrigin=eyJpIjoiZjNiM2... ) Issue Type: Bug Assignee: Unassigned Components: hibernate-core Created: 11/May/2023 01:13 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The mapping: @ManyToOne @JoinTable Publisher publisher; is currently disallowed by{{ColumnsBuilder.buildDefaultJoinColumnsForToOne()}}. There’s no good reason for this limitation, and we should be able to use an ImplicitJoinTableNameSource to infer a table name. ( https://hibernate.atlassian.net/browse/HHH-16583#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16583#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16532) Hibernate entity with @Any attribute throws a nullpointer exception when merging

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16532 ( https://hibernate.atlassian.net/browse/HHH-16532?atlOrigin=eyJpIjoiZTViNT... ) Re: Hibernate entity with @Any attribute throws a nullpointer exception when merging ( https://hibernate.atlassian.net/browse/HHH-16532?atlOrigin=eyJpIjoiZTViNT... ) Another reproducer can be found here: https://github.com/dirkniblick/polymorphWithoutSpringboot ( https://hibernate.atlassian.net/browse/HHH-16532#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16532#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16573) Embeddable element collection with updateable = false leads to NullPointerException

by Čedomir Igaly (JIRA)

Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16573 ( https://hibernate.atlassian.net/browse/HHH-16573?atlOrigin=eyJpIjoiYWFhYT... ) Re: Embeddable element collection with updateable = false leads to NullPointerException ( https://hibernate.atlassian.net/browse/HHH-16573?atlOrigin=eyJpIjoiYWFhYT... ) You can make your example more “interesting” by adding two embeddables in first tx, insert third one between those two in second tx, and finally check thier values in third tx. ( https://hibernate.atlassian.net/browse/HHH-16573#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16573#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#100225- sha1:84d3b45 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15929) Mapping jsonb of different types in a class inheritance hierarchy does not work.

by dan (JIRA)

dan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63503bc... ) *commented* on HHH-15929 ( https://hibernate.atlassian.net/browse/HHH-15929?atlOrigin=eyJpIjoiNjcwYW... ) Re: Mapping jsonb of different types in a class inheritance hierarchy does not work. ( https://hibernate.atlassian.net/browse/HHH-15929?atlOrigin=eyJpIjoiNjcwYW... ) I am also seeing this with 6.2.0.Final (via Quarkus 3.0.2.Final et al). In my case I have subclasses using custom user types to SerDe via Jackson from postgres jsonb columns. Otherwise the symptoms are the same. In debugging I discovered what I believe to be the source of where it all goes wrong. When an EntityPersister is being constructed (via AbstractEntityPersister#initOrdinaryPropertyPaths(...) there are multiple entries ( https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/m... ) for the same column name in the subclassProperty*Closure(s). This is fine except that AbstractPropertyMapping#addPropertyPath(...) drops duplicate registrations ( https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/m... ) when the types are not association types, thus the first discovered subclass’s mapping is chosen. Hope that helps! ( https://hibernate.atlassian.net/browse/HHH-15929#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15929#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Incorrect enhancement for PROPERTY attributes with mismatched field and method names

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=eyJpIjoiN2VjZjFlMDBj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiN2VjZj... ) HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiN2VjZj... ) Incorrect enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiN2VjZj... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Summary: Bad Incorrect enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16069) Skip CDI for Hibernate extensions by default

by Petula Lau (JIRA)

Petula Lau ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16069 ( https://hibernate.atlassian.net/browse/HHH-16069?atlOrigin=eyJpIjoiNjUwZG... ) Re: Skip CDI for Hibernate extensions by default ( https://hibernate.atlassian.net/browse/HHH-16069?atlOrigin=eyJpIjoiNjUwZG... ) Hi - this is happening to me as well - but it was when I migrated from hibernate 5.5.3 to 5.6.x on wildfly 23 However the error is a nullpointerexception at start up JpaCompliantLifecycleStrategy line 109 (beanmanager is null) I noticed that this breakpoint is not reached in 5.5.3 during startup, but only on 5.6.x version In the end I have given up and rolled back - is migrating to hibernate 6 the only answer? Cheers ( 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Bad enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiNWQ3Mm... ) Re: Bad enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiNWQ3Mm... ) That’s good to know, thanks Rafael Winterhalter ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) ! I’ll work on a version of that AccessType resolution based on TypeDescription rather than Class. Might be interesting to encode the resolved AccessType into the enhanced class adding the @Access annotation if not present. That would speed up building the metadata at runtime. ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Bad enhancement for PROPERTY attributes with mismatched field and method names

by Rafael Winterhalter (JIRA)

Rafael Winterhalter ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOWE4Mz... ) Re: Bad enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOWE4Mz... ) Byte Buddy offers all reflection methods (without invoke) via its TypeDescription API. So at least it should be easy to port. The type pool should also resolve all libked classes from the supplied class path. ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Bad enhancement for PROPERTY attributes with mismatched field and method names

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=eyJpIjoiN2Q0NTYyN2I0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiN2Q0NT... ) HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiN2Q0NT... ) Bad enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiN2Q0NT... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider the model : {code:java}@Entity public static class Spouse { ... private String last; @Id Integer getId() {...}; String getLastName() {...}; void setLastName(String name) {...}; }{code} Here, we have PROPERTY access (getter and setter) because of the placement of {{(a)Id}}. which in turn means that we have a persistent attribute named {{lastName}}based on the getter method name. This confuses the enhancer which always works from the field name. Here, it thinks the persistent attribute is named {{last}}. ---- Jakarta EE 10 TCK test jpa/core/query/flushmode ( #flushModeTest5 ) [https://github.com/jakartaee/platform-tck/blob/master/src/com/sun/ts/test...] fails. The tests that fail with vehicle names: * flushModeTest5_from_appmanagedNoTx * flushModeTest5_from_pmservlet * flushModeTest5_from_puservlet * flushModeTest5_from_stateless3 The same tests pass with bytecode enhancement disabled. The test output contains: [javatest.batch] ^[[0m^[[0m12:24:15,206 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Wrong collection size returned (expected 1, got 0) [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Wrong size returned, expected PKs of (11), got PKs of () [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Did not get expected results. Expected 1 reference, got: 0 [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: flushModeTest5 failed [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Test case throws exception: flushModeTest5 failed [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Exception at: [javatest.batch] ^[[0m^[[0m12:24:15,208 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: com.sun.ts.lib.harness.EETest$Fault: flushModeTest5 failed [javatest.batch] ^[[0m^[[0m12:24:15,209 INFO [stdout] (Thread-197) at deployment.jpa_core_query_flushmode_vehicles.ear.jpa_core_query_flushmode_appmanagedNoTx_vehicle_ejb.jar// ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Bad enhancement for PROPERTY attributes with mismatched field and method names

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=eyJpIjoiOGRkMTlkMGRm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOGRkMT... ) HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOGRkMT... ) Bad enhancement for PROPERTY attributes with mismatched field and method names ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOGRkMT... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider the model : {code:java}@Entity public static class Spouse { ... private String last; @Id Integer getId() {...}; String getLastName() {...}; void setLastName(String name) {...}; }{code} Here, we have PROPERTY access (getter and setter) because of the placement of {{(a)Id}}. which in turn means that we have a persistent attribute named {{lastName}}based on the getter method name. This confuses the enhancer which always works from the field name. Here, it thinks the persistent attribute is named {{last}}. ---- Jakarta EE 10 TCK test jpa/core/query/flushmode ( #flushModeTest5 ) [https://github.com/jakartaee/platform-tck/blob/master/src/com/sun/ts/test...] fails. The tests that fail with vehicle names: * flushModeTest5_from_appmanagedNoTx * flushModeTest5_from_pmservlet * flushModeTest5_from_puservlet * flushModeTest5_from_stateless3 The same tests pass with bytecode enhancement disabled. The test output contains: [javatest.batch] ^[[0m^[[0m12:24:15,206 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Wrong collection size returned (expected 1, got 0) [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Wrong size returned, expected PKs of (11), got PKs of () [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Did not get expected results. Expected 1 reference, got: 0 [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: flushModeTest5 failed [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Test case throws exception: flushModeTest5 failed [javatest.batch] ^[[0m^[[0m12:24:15,207 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: Exception at: [javatest.batch] ^[[0m^[[0m12:24:15,208 INFO [stdout] (Thread-197) 05-02-2023 12:24:15: SVR-ERROR: com.sun.ts.lib.harness.EETest$Fault: flushModeTest5 failed [javatest.batch] ^[[0m^[[0m12:24:15,209 INFO [stdout] (Thread-197) at deployment.jpa_core_query_flushmode_vehicles.ear.jpa_core_query_flushmode_appmanagedNoTx_vehicle_ejb.jar// ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) Bad enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16572) jpa/core/query/flushmode TCK test failures

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiY2U4Yj... ) Re: jpa/core/query/flushmode TCK test failures ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiY2U4Yj... ) > > > > I remember porting this from the Javassist implementation back in the > days, I can hardly imagine that I came up with this approach. > > The older Javassist enhancer had the same problem when we checked. > > > > The decision to place this field name is made here: https://github.com/hibernate/hibernate-orm/blob/2d345fc04bf4c2df1d76d5f89... > > > That’s one place. It is a problem in many of the places persistentField.getName() is used. > > > > Is the required information available at this point? > > Unfortunately not. Largely this boils down to being able to understand the jakarta.persistence.AccessType in effect for each attribute, which is not a simple determination as we have to look across all fields and methods of the class and its supers. We have code that does this of course, but it is all based on the Class and reflection. And for enhancement, I’m not sure we always have access to all classes when enhancing one. ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16542) Bad get/is handling with bytecode enhancement

by Steve Ebersole (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Jan Schatteman (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Jan Schatteman (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjQ1NzBkMDdk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYjQ1Nz... ) HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYjQ1Nz... ) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYjQ1Nz... ) Issue Type: Bug Assignee: Unassigned Created: 10/May/2023 08:38 AM Environment: Seems there is a change that breaks backward compatibility... I have some entity classes preprocessing that dynamically adds filter defs annotation based on some conditions So it can happen that entity A will have filterDefs filterA and FilterB and entity B will have filterDef filterA It was working in hibernate version 3-5 and in 6.1.7 in 6.2.2 it gives me an error. Can you please revert that condition or outline a context for filterDefs is it class(seems not), package, persistent unit ? I have 4 persistent units.. and a single instance of class transformer that intercepts class loading and it doesn't know anything about persistent unit that class belongs :( And maybe update docs as I didn't find any information about this requirement and some motivation of why it was added Priority: Major Reporter: Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (BVAL-787) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *created* an issue Bean Validation ( https://hibernate.atlassian.net/browse/BVAL?atlOrigin=eyJpIjoiY2E1NjljMmZ... ) / Bug ( https://hibernate.atlassian.net/browse/BVAL-787?atlOrigin=eyJpIjoiY2E1Njl... ) BVAL-787 ( https://hibernate.atlassian.net/browse/BVAL-787?atlOrigin=eyJpIjoiY2E1Njl... ) Alias XXX used for multiple from-clause elements error when executing query with 2 level join ( https://hibernate.atlassian.net/browse/BVAL-787?atlOrigin=eyJpIjoiY2E1Njl... ) Issue Type: Bug Assignee: Unassigned Created: 10/May/2023 08:22 AM Environment: java 17, spring boot 3, hibernate 6.1.7 Priority: Blocker Reporter: Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) Seems there is a bug somewhere either in query parsing or joins processing in hibernate 6.1.7+ That code & query works fine in all prev. versions from hibernate 3 to 5 I have a named query: ``` <query>SELECT COUNT(adminPermission) FROM org.broadleafcommerce.openadmin.server.security.domain.AdminPermission adminPermission LEFT OUTER JOIN adminPermission.allChildPermissions childPermission LEFT OUTER JOIN childPermission.qualifiedEntities childQualifiedEntity LEFT OUTER JOIN adminPermission.qualifiedEntities qualifiedEntity LEFT OUTER JOIN adminPermission.allRoles role LEFT OUTER JOIN role.allUsers roleUser LEFT OUTER JOIN adminPermission.allUsers permissionUser WHERE (roleUser = :adminUser OR permissionUser = :adminUser) AND (adminPermission.type = :type OR adminPermission.type = 'ALL' OR childPermission.type = :type OR childPermission.type = 'ALL') AND (qualifiedEntity.ceilingEntityFullyQualifiedName = :ceilingEntity OR childQualifiedEntity.ceilingEntityFullyQualifiedName = :ceilingEntity) </query> ``` There OneToMany and ManyToMany through JoinTable asossiations it this is important I debugged a bit and see that it processes condition (roleUser = :adminUser OR permissionUser = :adminUser) and finds a join LEFT OUTER JOIN role.allUsers roleUser so it finds alias "roleUser", logic goes into org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#visitSetJoin where it does: final SqmSetJoin copy = new SqmSetJoin<>( findSqmFromCopy( join.getLhs() ), so join.getLhs() will return another join LEFT OUTER JOIN adminPermission.allRoles role so it finds alias "role" And in org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#findSqmFromCopy it does return (X) sqmFrom.accept( this ); So it will do a recursive call that will eventually come to org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#visitSetJoin again, where it will process join with alias "role" and in org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#visitJoins will register that alias, and also it will do join.visitSqmJoins( sqmJoin -> sqmJoin.accept( this ) ); where "role" join will reference "roleUser" join via joins.forEach( consumer ); in org.hibernate.query.sqm.tree.domain.AbstractSqmFrom#visitSqmJoins it will process it and also registers via org.hibernate.query.hql.internal.SqmPathRegistryImpl#register(org.hibernate.query.sqm.tree.domain.SqmPath<?>) so now registry map knows about "role" and "roleUser" joins and recursion ends and it eventually continues to process "roleUse" join - where we start recursion... and it again will attempt to register org.hibernate.query.hql.internal.SqmPathRegistryImpl#register(org.hibernate.query.sqm.tree.domain.SqmPath<?>) where it fails with exception... So there is something wrong on how "multi-level joins" are handled. ( https://hibernate.atlassian.net/browse/BVAL-787#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/BVAL-787#add-comment?atlOrigin=eyJ... ) 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16498) Hibernate DDL validation fails on enum database column type

by Čedomir Igaly (JIRA)

Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16498 ( https://hibernate.atlassian.net/browse/HHH-16498?atlOrigin=eyJpIjoiYjJlOT... ) Re: Hibernate DDL validation fails on enum database column type ( https://hibernate.atlassian.net/browse/HHH-16498?atlOrigin=eyJpIjoiYjJlOT... ) Fix for 6.2 - pull request 6541 ( https://github.com/hibernate/hibernate-orm/pull/6541 ) ( https://hibernate.atlassian.net/browse/HHH-16498#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16498#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HV-1847) Method Constraints declared on interfaces are not being validated unless implementation contains validation annotations

by Guillaume Smet (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16549) NullPointerException when calling LoadQueryInfluencers#isFetchProfileEnabled

by Jan Schatteman (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Felix Desyatirikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Felix Desyatirikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Felix Desyatirikov (JIRA)

Felix Desyatirikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGVhMzFkODRk... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16580?atlOrigin=eyJpIjoiNGVhMz... ) HHH-16580 ( https://hibernate.atlassian.net/browse/HHH-16580?atlOrigin=eyJpIjoiNGVhMz... ) Some typos in org.hibernate.query.sqm ( https://hibernate.atlassian.net/browse/HHH-16580?atlOrigin=eyJpIjoiNGVhMz... ) Issue Type: Improvement Affects Versions: 6.2.2 Assignee: Unassigned Components: query-hql Created: 10/May/2023 06:59 AM Priority: Trivial Reporter: Felix Desyatirikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) org.hibernate.query.sqm.function.FunctionKind:...kind of a function... ->...kind of function... org.hibernate.query.sqm.produce.function.ArgumentsValidator:...provided to a HQL... ->...provided to an HQL... org.hibernate.query.sqm.produce.function.StandardFunctionReturnTypeResolvers:...allows the context-impled expression... ->...allows the context-implied expression... org.hibernate.query.sqm.tree.expression.SqmModifiedSubQueryExpression:...modifier appplied to a subquery... ->...modifier applied to a subquery... org.hibernate.query.sqm.mutation.internal.temptable.TableBasedDeleteHandler:...Getters for Hibernat Reactive... ->...Getters for Hibernate Reactive... ( https://hibernate.atlassian.net/browse/HHH-16580#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16580#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16549) NullPointerException when calling LoadQueryInfluencers#isFetchProfileEnabled

by Christian Beikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16579) Add constructor for CockroachDialect that parses the version without querying the db

by Davide D'Alto (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16579) Add constructor for CockroachDialect that parses the version without querying the db

by Davide D'Alto (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16579) Add constructor for CockroachDialect that parses the version without querying the db

by Davide D'Alto (JIRA)

Davide D'Alto ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGRmN2M1MjI3... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-16579?atlOrigin=eyJpIjoiNGRmN2... ) HHH-16579 ( https://hibernate.atlassian.net/browse/HHH-16579?atlOrigin=eyJpIjoiNGRmN2... ) Add constructor for CockroachDialect that parses the version without querying the db ( https://hibernate.atlassian.net/browse/HHH-16579?atlOrigin=eyJpIjoiNGRmN2... ) Issue Type: New Feature Assignee: Unassigned Created: 10/May/2023 06:39 AM Priority: Major Reporter: Davide D'Alto ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) For HIbernate Reactive, we need a constructor that parses the version returned by the database without running a query. That’s because ORM uses JDBC for the query ( https://hibernate.atlassian.net/browse/HHH-16579#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16579#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16578) Incorrect validation error for tinyint, but and datetime

by Christian Beikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HV-1948) Incorrect validation error for tinyint, but and datetime

by Max (JIRA)

Max ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *created* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiYmY3NjQ0ODAzO... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1948?atlOrigin=eyJpIjoiYmY3NjQ0... ) HV-1948 ( https://hibernate.atlassian.net/browse/HV-1948?atlOrigin=eyJpIjoiYmY3NjQ0... ) Incorrect validation error for tinyint, but and datetime ( https://hibernate.atlassian.net/browse/HV-1948?atlOrigin=eyJpIjoiYmY3NjQ0... ) Issue Type: Bug Affects Versions: 8.0.0.Final Assignee: Unassigned Attachments: hybernate-validation-error-spring-boot.zip Components: validators Created: 10/May/2023 06:02 AM Environment: Spring Boot, Java 17/19, MySQL Priority: Major Reporter: Max ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) See https://discourse.hibernate.org/t/error-in-native-query-where-column-is-m.... For some MySQL data types full column definition results in the following exception (that stops a spring boot application from starting): org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: wrong column type encountered in column [level] in table [test_data] ; found tinyint (Types#TINYINT) ( #TINYINT) ) , but expecting tinyint unsigned default '0' (Types#INTEGER) ( #INTEGER) ) For example, for this table: CREATE TABLE `test_data` ( `id` int unsigned NOT NULL AUTO_INCREMENT, `level` tinyint unsigned DEFAULT '0', `delete_date` datetime DEFAULT '1970-01-01 00:00:00', PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; this is fine: @Column(name = "level", columnDefinition = "tinyint") private int level; but this results in the exception mentioned above: @Column(name = "level", columnDefinition = "tinyint UNSIGNED DEFAULT '0'") private int level; Same for datetime, bit and maybe others. Creating this issue on request by beikov. hybernate-validation-error-spring-boot.zip ( https://hibernate.atlassian.net/secure/attachment/50369/50369_hybernate-v... ) ( https://hibernate.atlassian.net/browse/HV-1948#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1948#add-comment?atlOrigin=eyJp... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15614) add the complete set of standard HQL "standard" functions to HibernateCriteriaBuilder

by Christian Beikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16576) problem in query involving union on MariaDB and Oracle

by Christian Beikov (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16573) Embeddable element collection with updateable = false leads to NullPointerException

by Andrea Boriero (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16569) Batch fetch leads to some collections to be wrongly initialized with empty due to wrong generated SQL

by Andrea Boriero (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16559) Batch fetch does not initialize bi-directional entity in HQL

by Marco Belladelli (JIRA)

3 years, 2 months

1
0
0 / 0

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

by Prashant Guleria (JIRA)

Prashant Guleria ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYmMyZD... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYmMyZD... ) Thanks for you reply. I went through https://docs.jboss.org/hibernate/orm/6.2/migration-guide/migration-guide.... It seems that these properties are set to *true* by default when we apply the enhancement plugin. ( https://hibernate.atlassian.net/secure/attachment/50368/50368_image-20230... ) I am going to test the issue later today, I’ll share my findings tomorrow. Thanks ( 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16549) NullPointerException when calling LoadQueryInfluencers#isFetchProfileEnabled

by Jan Schatteman (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-1615) GROUP BY entity does not work

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-1615 ( https://hibernate.atlassian.net/browse/HHH-1615?atlOrigin=eyJpIjoiZTE4Mzd... ) Re: GROUP BY entity does not work ( https://hibernate.atlassian.net/browse/HHH-1615?atlOrigin=eyJpIjoiZTE4Mzd... ) Please try again with 6.2.2.Final. We fixed a few edge cases in the meantime. ( https://hibernate.atlassian.net/browse/HHH-1615#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-1615#add-comment?atlOrigin=eyJ... ) 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4845) Have a dedicated docvalue field for the root document id in the Lucene backend's document

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4845 ( https://hibernate.atlassian.net/browse/HSEARCH-4845?atlOrigin=eyJpIjoiODY... ) Re: Have a dedicated docvalue field for the root document id in the Lucene backend's document ( https://hibernate.atlassian.net/browse/HSEARCH-4845?atlOrigin=eyJpIjoiODY... ) Note Marko already implemented this but for now we reverted it for downstream reasons. Re-implementing it should be as easy as reverting this commit: https://github.com/hibernate/hibernate-search/commit/1d9b7f8104b0295f8ace... ( https://hibernate.atlassian.net/browse/HSEARCH-4845#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4845#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16573) Embeddable element collection with updateable = false leads to NullPointerException

by Andrea Boriero (JIRA)

3 years, 2 months

1
0
0 / 0

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

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYzMxZj... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYzMxZj... ) the properties have been deprecated because the new Gradle plugins guidelines see https://docs.gradle.org/current/userguide/lazy_configuration.html#lazy_co... , but this should not mean that the enhancement should not work. By the way to avoid the deprecation I think you should use hibernate{ enhancement { enableLazyInitialization.set( true ) enableDirtyTracking.set(true) } } ( 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16498) Hibernate DDL validation fails on enum database column type

by Christian Beikov (JIRA)

3 years, 2 months

1
0
0 / 0

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

by Prashant Guleria (JIRA)

Prashant Guleria ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiMjRhMm... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiMjRhMm... ) Hi, It seems that hibenrate enhancements are being deprectaed and byte-code enhancememt is not workin gin my code after I upgraded to 6.2.2.Final. I am looking for a work-around this. I’ll update once bytecode enhancment works. ( 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16547) New `hibernate.jpa.compliance.delete` setting

by Prithvi singh (JIRA)

Prithvi singh ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-16547 ( https://hibernate.atlassian.net/browse/HHH-16547?atlOrigin=eyJpIjoiODQ1MW... ) Re: New `hibernate.jpa.compliance.delete` setting ( https://hibernate.atlassian.net/browse/HHH-16547?atlOrigin=eyJpIjoiODQ1MW... ) @Steve Ebersole . Could you please review my pull request. Thanks. ( https://hibernate.atlassian.net/browse/HHH-16547#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16547#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4852) Please migrate from javax to jakarta to make hibernate search compatible with Spring 6

by Yoann Rodière (JIRA)

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4852) Please migrate from javax to jakarta to make hibernate search compatible with Spring 6

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4852 ( https://hibernate.atlassian.net/browse/HSEARCH-4852?atlOrigin=eyJpIjoiNDd... ) Re: Please migrate from javax to jakarta to make hibernate search compatible with Spring 6 ( https://hibernate.atlassian.net/browse/HSEARCH-4852?atlOrigin=eyJpIjoiNDd... ) Way ahead of you 🙂 This is already available using separate Maven artifacts: * With ORM 5: https://docs.jboss.org/hibernate/stable/search/reference/en-US/html_singl... * With ORM 6: https://docs.jboss.org/hibernate/stable/search/reference/en-US/html_singl... In the future, for questions, please use stackoverflow or our forums ( https://discourse.hibernate.org/c/hibernate-search/6 ). Closing. ( https://hibernate.atlassian.net/browse/HSEARCH-4852#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4852#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4852) Please migrate from javax to jakarta to make hibernate search compatible with Spring 6

by Maurice (JIRA)

Maurice ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b0057d... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMTY5ZWQ5... ) / Bug ( https://hibernate.atlassian.net/browse/HSEARCH-4852?atlOrigin=eyJpIjoiMTY... ) HSEARCH-4852 ( https://hibernate.atlassian.net/browse/HSEARCH-4852?atlOrigin=eyJpIjoiMTY... ) Please migrate from javax to jakarta to make hibernate search compatible with Spring 6 ( https://hibernate.atlassian.net/browse/HSEARCH-4852?atlOrigin=eyJpIjoiMTY... ) Issue Type: Bug Affects Versions: 6.2.0.Alpha2 Assignee: Unassigned Components: mapper-orm Created: 10/May/2023 00:23 AM Environment: java 17, windows 11 mysql 8 Labels: Hibernate-jpa2.1, Priority: Major Reporter: Maurice ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b0057d... ) I am trying to create a session with org.hibernate.search.mapper.orm.Search.session(entityManager). However i can't because the session method takes a javax.persistence.EntityManager whereas Spring/Hibernate 6 uses jakarta.persistence.EntityManager instead. I've also noticed that hibernate search mapper still uses hibernate 5 as a dependency. This issue is preventing me from fully upgrading to spring 6, even though it has been available since november 2022. Could you please replace javax with jakarta and replace the hibernate 5 dependency with hibernate 6? ( https://hibernate.atlassian.net/browse/HSEARCH-4852#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4852#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

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

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYzhhOW... ) Re: Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiYzhhOW... ) Hi Prashant Guleria ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , can you please try if the issue persist also with the latest version of Hibernate, 6.2.2.Final thanks? In case it still fails can you please provide a test case? Thanks ( 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15929) Mapping jsonb of different types in a class inheritance hierarchy does not work.

by Thomas Bosch (JIRA)

Thomas Bosch ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c19f84... ) *commented* on HHH-15929 ( https://hibernate.atlassian.net/browse/HHH-15929?atlOrigin=eyJpIjoiNzBmMD... ) Re: Mapping jsonb of different types in a class inheritance hierarchy does not work. ( https://hibernate.atlassian.net/browse/HHH-15929?atlOrigin=eyJpIjoiNzBmMD... ) With 6.2.2.Final the problem still persists. ( https://hibernate.atlassian.net/browse/HHH-15929#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15929#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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

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

by Prashant Guleria (JIRA)

Prashant Guleria ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOGMzN2EzZDlm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiOGMzN2... ) HHH-16577 ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiOGMzN2... ) Index Out of Bound Exception ( https://hibernate.atlassian.net/browse/HHH-16577?atlOrigin=eyJpIjoiOGMzN2... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Attachments: image-20230510-070227 (6355fa57-062e-465a-961e-9ef79cc90026).png, image-20230510-070227.png Components: hibernate-core Created: 10/May/2023 00:07 AM Environment: Postgres 14 , JAVA 17, MAC OS and Linux OS, Hibenrate 6.1.17.Final with Spring Boot 3.0.4 Labels: Lazy byte-code-enhancement bytecode core enhancement lazy Priority: Major Reporter: Prashant Guleria ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In function {{protected Object handleRead(Object target, String attributeName, Object value) }} defined in class public class EnhancementAsProxyLazinessInterceptor extends AbstractLazyLoadInterceptor , I am getting Index Out of bound exception. If you see assignment as writtenValues = new Object [writtenFieldNames.size()] ; In my case the size of writtenFieldNames is 1, But the size variable has value 23 which comes from final int size = entityPersister.getNumberOfAttributeMappings() In entityPersister my field is present at index 1, but writtenValues can contain only 1 element at index 0. and throws out of bond exception. if ( writtenFieldName.contains( entityPersister.getAttributeMapping( index ).getAttributeName() ) ) { Index 1 out of bounds for length 1 java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1 at org.hibernate.bytecode.enhance.spi.interceptor.EnhancementAsProxyLazinessInterceptor.lambda$handleRead$0(EnhancementAsProxyLazinessInterceptor.java:152) at org.hibernate.bytecode.enhance.spi.interceptor.EnhancementHelper.performWork(EnhancementHelper.java:206) at org.hibernate.bytecode.enhance.spi.interceptor.EnhancementAsProxyLazinessInterceptor.handleRead(EnhancementAsProxyLazinessInterceptor.java:102) at org.hibernate.bytecode.enhance.spi.interceptor.AbstractInterceptor.readObject(AbstractInterceptor.java:152) ( https://hibernate.atlassian.net/secure/attachment/50365/50365_image-20230... ) ( 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#100225- sha1:55ea0c5 )

3 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2023