June 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16744) Wrong class created when reusing a join column for different entities in multiple ManyToOne

by Guillaume Toison (JIRA)

Guillaume Toison ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjc2ZDA4NzZj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16744?atlOrigin=eyJpIjoiZjc2ZD... ) HHH-16744 ( https://hibernate.atlassian.net/browse/HHH-16744?atlOrigin=eyJpIjoiZjc2ZD... ) Wrong class created when reusing a join column for different entities in multiple ManyToOne ( https://hibernate.atlassian.net/browse/HHH-16744?atlOrigin=eyJpIjoiZjc2ZD... ) Issue Type: Bug Affects Versions: 6.2.4 Assignee: Unassigned Components: hibernate-core Created: 03/Jun/2023 13:47 PM Priority: Major Reporter: Guillaume Toison ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) Consider the following abridged model (please note the reused food_id column and the self-referencing @ManyToOne in Fruit and Cheese ): class Container { } class FruitContainer extends Container { @ManyToOne @JoinColumn(name = "food_id" ) @Fetch(FetchMode.SELECT) private Fruit fruit; } class CheeseContainer extends Container { @ManyToOne @JoinColumn(name = "food_id" ) @Fetch(FetchMode.SELECT) private Cheese cheese; } class Food { } class Fruit extends Food { @ManyToOne @Fetch(FetchMode.SELECT) private Fruit bestPairedWith; } class Cheese extends Food { @ManyToOne @Fetch(FetchMode.SELECT) private Cheese bestPairedWith; } When batch-loading several Container objects, Hibernate seems to create the wrong class (a Cheese instead of a Fruit ) I’m not sure if reusing a column in different branches of an inheritance tree is supported but this seemed to work in Hibernate 5. In Hibernate 6 an initializer seems to be associated with the column during the batch load but it only works for one of the types. ( https://hibernate.atlassian.net/browse/HHH-16744#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16744#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4864) Add fuzzy query in Hibernate Search 6

by Nguyen Duc Thang (JIRA)

Nguyen Duc Thang ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d367f... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYTY5NjFl... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiYTY... ) HSEARCH-4864 ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiYTY... ) Add fuzzy query in Hibernate Search 6 ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiYTY... ) Change By: Nguyen Duc Thang ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d367f... ) I am using hibernate search with Elasticsearch. The problem is i must use a fuzzy query directly instead of a match query with fuzziness options, because Elasticsearch do not allow for match query with fuzziness with Ngram token. [Reference link here|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query.html#6b0288acb739c4667d41339e5100c327]. Will there be support for fuzzy query in the future? link ( https://hibernate.atlassian.net/browse/HSEARCH-4864#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4864#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16742) ArrayIndexOutOfBoundsException when calling Tuple.getElements()

by Gavin King (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16742) ArrayIndexOutOfBoundsException when calling Tuple.getElements()

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16742 ( https://hibernate.atlassian.net/browse/HHH-16742?atlOrigin=eyJpIjoiYzNjOT... ) Re: ArrayIndexOutOfBoundsException when calling Tuple.getElements() ( https://hibernate.atlassian.net/browse/HHH-16742?atlOrigin=eyJpIjoiYzNjOT... ) OK, that should be fixed now. ( https://hibernate.atlassian.net/browse/HHH-16742#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16742#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16022) bad error reporting of parsing failures

by Gavin King (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16697) CALCULATED FIELDS in createNativeQuery doExtract integer insted of BigDecimals.

by Ralf Grewe (JIRA)

Ralf Grewe ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *commented* on HHH-16697 ( https://hibernate.atlassian.net/browse/HHH-16697?atlOrigin=eyJpIjoiYjNkNz... ) Re: CALCULATED FIELDS in createNativeQuery doExtract integer insted of BigDecimals. ( https://hibernate.atlassian.net/browse/HHH-16697?atlOrigin=eyJpIjoiYjNkNz... ) Oracle JDBC Driver always returns zero for both “ResultSetMetaData.getScale()” and “ResultSetMetaData.getPrecision()” in case you use aggregate functions. Oracle support document 1587538.1 states that Precision and Scale are not available when using SQL functions and that this is expected behaviour, e.g.: if you create the following VIEW: SQL> create view <VIEW NAME> as select max(<COLUMN NAME>) max_c1 from <TABLE NAME>; …and then run a “DESCRIBE” on the VIEW: SQL> desc <VIEW NAME> Name Null? Type ----------------------------------------- -------- ---------------------------- MAX_C1 NUMBER …you will notice that no Scale nor Precision has been packaged with the datum which in return means that JDBC also just returns the datatype given by the server. For 'normal' columns the data dictionary core catalogs are queried to obtain information like precision and scale . However, since for aggregate function the result of such functions do not exist in these catalogs, then they are unknown. Oracle Document 1946626.1 delivers some details on how to interpret the precision and scale values ( https://hibernate.atlassian.net/browse/HHH-16697#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16697#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4864) Add fuzzy query in Hibernate Search 6

by Nguyen Duc Thang (JIRA)

Nguyen Duc Thang ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d367f... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiN2RmYWIy... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiN2R... ) HSEARCH-4864 ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiN2R... ) Add fuzzy query in Hibernate Search 6 ( https://hibernate.atlassian.net/browse/HSEARCH-4864?atlOrigin=eyJpIjoiN2R... ) Issue Type: New Feature Affects Versions: 6.1.8.Final Assignee: Unassigned Components: backend-elasticsearch, query Created: 02/Jun/2023 20:45 PM Environment: openjdk 17.0.7 Ubuntu 20.04 Elasticsearch 7.17 Hibernate-core 6.2.3 Priority: Major Reporter: Nguyen Duc Thang ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d367f... ) I am using hibernate search with Elasticsearch. The problem is i must use a fuzzy query directly instead of a match query with fuzziness options, because Elasticsearch do not allow for match query with fuzziness with Ngram token. Reference link here ( https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl... ). Will there be support for fuzzy query in the future?link ( https://hibernate.atlassian.net/browse/HSEARCH-4864#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4864#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HV-1953) The problem of verifying the maximum length of email addresses in email verification

by Ge liang (JIRA)

Ge liang ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *created* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiNzI0ZWY2ZWMzO... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1953?atlOrigin=eyJpIjoiNzI0ZWY2... ) HV-1953 ( https://hibernate.atlassian.net/browse/HV-1953?atlOrigin=eyJpIjoiNzI0ZWY2... ) The problem of verifying the maximum length of email addresses in email verification ( https://hibernate.atlassian.net/browse/HV-1953?atlOrigin=eyJpIjoiNzI0ZWY2... ) Issue Type: Bug Assignee: Unassigned Components: validators Created: 02/Jun/2023 18:18 PM Priority: Major Reporter: Ge liang ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) In the email validator，the email’s max length is 64+1+255=320. But the email’s max length is 256 in rfc 5321( 4.5.3.1.3) : https://datatracker.ietf.org/doc/html/rfc5321#section-4.5.3.1.3 ，Except for the angle brackets (<>) before and after the email address, the maximum length should be 254? ( https://hibernate.atlassian.net/browse/HV-1953#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1953#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16742) ArrayIndexOutOfBoundsException when calling Tuple.getElements()

by Jan Schatteman (JIRA)

Jan Schatteman ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16742 ( https://hibernate.atlassian.net/browse/HHH-16742?atlOrigin=eyJpIjoiYmQ4ZT... ) Re: ArrayIndexOutOfBoundsException when calling Tuple.getElements() ( https://hibernate.atlassian.net/browse/HHH-16742?atlOrigin=eyJpIjoiYmQ4ZT... ) Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I ran a very quick test on your PR, and indeed the AIOOBE is gone, and the TupleElements list now contains 2 elements. However , those are identical elements (as in, the same object reference), so perhaps we’re not quite there yet. ( https://hibernate.atlassian.net/browse/HHH-16742#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16742#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:e03cc87 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16697) CALCULATED FIELDS in createNativeQuery doExtract integer insted of BigDecimals.

by Isaac Vásquez (JIRA)

2 years, 10 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 June 2023