February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16182) JPA derived query methods failing when boolean mapping using YesNoConverter

by Chacko Mathew (JIRA)

Chacko Mathew ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63eb773... ) *commented* on HHH-16182 ( https://hibernate.atlassian.net/browse/HHH-16182?atlOrigin=eyJpIjoiZDY0OG... ) Re: JPA derived query methods failing when boolean mapping using YesNoConverter ( https://hibernate.atlassian.net/browse/HHH-16182?atlOrigin=eyJpIjoiZDY0OG... ) This could be an issue in Spring Data JPA module, I created an issue in their tracker. ( https://hibernate.atlassian.net/browse/HHH-16182#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16182#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#100216- sha1:a1e7611 )

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16187) Recursive join fetch

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDg2ODY1YzM0... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-16187?atlOrigin=eyJpIjoiZDg2OD... ) HHH-16187 ( https://hibernate.atlassian.net/browse/HHH-16187?atlOrigin=eyJpIjoiZDg2OD... ) Recursive join fetch ( https://hibernate.atlassian.net/browse/HHH-16187?atlOrigin=eyJpIjoiZDg2OD... ) Issue Type: New Feature Assignee: Unassigned Components: hibernate-core Created: 15/Feb/2023 07:53 AM Fix Versions: 6.wishlist Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Transitioning this over from the GH discussion ( https://github.com/hibernate/hibernate-orm/discussions/6100 ) : We added the recursive CTE construct to model the canonical way to do recursive queries in HQL, but I think it would be nice to extend this a bit. Here are a few ideas. The idea is that we introduce a new kind of join, a recursive join, which we translate to a recursive CTE. Recursive joins would only be allowed on self referencing @ManyToOne / @OneToMany(mappedBy) associations. If we want to support EAGER fetching of recursive associations we would probably need some sort of @RecursiveParent / @RecursiveChildren annotation to mark associations in an entity model, so that we can generate the proper query, but I guess we can ignore that for now. The really interesting part is when join fetching collections e.g. from Entity1 a recursive join fetch a.children , as that has an implication on the Fetch we generate and how we process results, since all nested collection will become initialized this way. ( https://hibernate.atlassian.net/browse/HHH-16187#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16187#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#100216- sha1:a1e7611 )

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16186) Duplicate entries in OneToMany relation after manual eagerly loading of entries

by T3rm1 (JIRA)

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16186) Duplicate entries in OneToMany relation after manual eagerly loading of entries

by T3rm1 (JIRA)

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16186) Duplicate entries in OneToMany relation after manual eagerly loading of entries

by T3rm1 (JIRA)

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16186) Duplicate entries in OneToMany relation after manual eagerly loading of entries

by T3rm1 (JIRA)

T3rm1 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTMzMTkzZjNi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16186?atlOrigin=eyJpIjoiYTMzMT... ) HHH-16186 ( https://hibernate.atlassian.net/browse/HHH-16186?atlOrigin=eyJpIjoiYTMzMT... ) Duplicate entries in OneToMany relation after manual eagerly loading of entries ( https://hibernate.atlassian.net/browse/HHH-16186?atlOrigin=eyJpIjoiYTMzMT... ) Change By: T3rm1 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I’m not sure if the title fits. I had trouble finding a good one. This bug leads to multiple duplicates appear in the list of a {{OneToMany}} relation that was initialized manually in order to prevent N+1 query problem. There are three entities, {{A}}, {{B}} and {{C}}. {{A <-1--1-> B}} {{B <-1--N-> C}} A has one B, B has multiple C. Loading is configured as lazy. *Given situation*: I have 4 {{A}}which all point to the same {{B}}. This {{B}}has two {{C}}. So if I do {{a.getB().getCList()}}the size should be 2. This works out of the box with lazy loading. However, if I add the following query, in order to load all {{C}}into the cache and a prevent N+1 query problem, then suddenly each {{B}}has *eight* entries of {{C}}. { noformat code:java }List<A> resultNotNeeded = entityManager.createQuery(""" select distinct a from A a join fetch a.b b left join fetch b.cList where a in (:aList) """, A.class) .setParameter("aList", aList) .setHint(org.hibernate.jpa.QueryHints.HINT_PASS_DISTINCT_THROUGH, "false") .getResultList();{ noformat code } It doesn’t make a difference if I remove the distinct and query hint. {{aList}}is just the list of the four a entities. A test case is attached. ( https://hibernate.atlassian.net/browse/HHH-16186#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16186#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#100216- sha1:a1e7611 )

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16186) Duplicate entries in OneToMany relation after manual eagerly loading of entries

by T3rm1 (JIRA)

T3rm1 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDUwMmIzNDUz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16186?atlOrigin=eyJpIjoiNDUwMm... ) HHH-16186 ( https://hibernate.atlassian.net/browse/HHH-16186?atlOrigin=eyJpIjoiNDUwMm... ) Duplicate entries in OneToMany relation after manual eagerly loading of entries ( https://hibernate.atlassian.net/browse/HHH-16186?atlOrigin=eyJpIjoiNDUwMm... ) Issue Type: Bug Assignee: Unassigned Attachments: bug.zip Created: 15/Feb/2023 06:24 AM Priority: Major Reporter: T3rm1 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I’m not sure if the title fits. I had trouble finding a good one. This bug leads to multiple duplicates appear in the list of a OneToMany relation that was initialized manually in order to prevent N+1 query problem. There are three entities, A , B and C. A < 1 1 > B B < 1 N > C A has one B, B has multiple C. Loading is configured as lazy. *Given situation* : I have 4 {{A}}which all point to the same B. This {{B}}has two C. So if I do {{a.getB().getCList()}}the size should be 2. This works out of the box with lazy loading. However, if I add the following query, in order to load all {{C}}into the cache and a prevent N+1 query problem, then suddenly each {{B}}has *eight* entries of C. List<A> resultNotNeeded = entityManager.createQuery(""" select distinct a from A a join fetch a.b b left join fetch b.cList where a in (:aList) """, A.class) .setParameter("aList", aList) .setHint(org.hibernate.jpa.QueryHints.HINT_PASS_DISTINCT_THROUGH, "false") .getResultList(); It doesn’t make a difference if I remove the distinct and query hint. {{aList}}is just the list of the four a entities. A test case is attached. ( https://hibernate.atlassian.net/browse/HHH-16186#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16186#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#100216- sha1:a1e7611 )

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16182) JPA derived query methods failing when boolean mapping using YesNoConverter

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16182 ( https://hibernate.atlassian.net/browse/HHH-16182?atlOrigin=eyJpIjoiYWFkNT... ) Re: JPA derived query methods failing when boolean mapping using YesNoConverter ( https://hibernate.atlassian.net/browse/HHH-16182?atlOrigin=eyJpIjoiYWFkNT... ) I pushed the test upstream - org.hibernate.userguide.mapping.basic.BooleanMappingTests#testQueryLiteralUsage I am not able to reproduce this bug - rejecting in lieu of reproducer ( https://hibernate.atlassian.net/browse/HHH-16182#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16182#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#100216- sha1:a1e7611 )

1 year, 11 months

1
0
0 / 0

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

by Steve Ebersole (JIRA)

1 year, 11 months

1
0
0 / 0

[JIRA] (HHH-16185) Standardize the date_trunc() function, emulating it for Dialects that don't support native versions

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGY3OTczNjg3... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16185?atlOrigin=eyJpIjoiNGY3OT... ) HHH-16185 ( https://hibernate.atlassian.net/browse/HHH-16185?atlOrigin=eyJpIjoiNGY3OT... ) Standardize the date_trunc() function, emulating it for Dialects that don't support native versions ( https://hibernate.atlassian.net/browse/HHH-16185?atlOrigin=eyJpIjoiNGY3OT... ) Issue Type: Improvement Assignee: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) Created: 15/Feb/2023 05:26 AM Priority: Minor Reporter: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) We should standardize the date_trunc() function, making it available for use to all Dialects. HSQLDB supports a trunc() function similar to Oracle and DB2. Microsoft SQL Server supports a datetrunc() function since version 16. Dialects that don't have a viable native function can use an emulation that leverages formatting the datetime to string and parsing back after truncating to the correct Temporal Unit. Also, fix the use of the function trunc() in Oracle and DB2 that requires transforming the Temporal Unit into a different format for most cases. ( https://hibernate.atlassian.net/browse/HHH-16185#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16185#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#100216- sha1:a1e7611 )

1 year, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2023