May 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16465) CTE query cycle attribute evaluated incorrectly on MSSQL

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16671) Unable to query key attribute that uses AttributeConverter

by Julien Ravet (JIRA)

Julien Ravet ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16671 ( https://hibernate.atlassian.net/browse/HHH-16671?atlOrigin=eyJpIjoiMDA5YT... ) Re: Unable to query key attribute that uses AttributeConverter ( https://hibernate.atlassian.net/browse/HHH-16671?atlOrigin=eyJpIjoiMDA5YT... ) Just to let you know I’m encountering the same kind of issue, trying to make YearMonth persistence work with Hibernate 6. @Type or @JavaType doens’t work either, even using a home made type or java Type (not the hypersistence one) I will post the corresponding error message and code today ( https://hibernate.atlassian.net/browse/HHH-16671#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16671#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:d82e018 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16671) Unable to query key attribute that uses AttributeConverter

by Piotr Przybylski (JIRA)

Piotr Przybylski ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16671 ( https://hibernate.atlassian.net/browse/HHH-16671?atlOrigin=eyJpIjoiNzY4Nm... ) Re: Unable to query key attribute that uses AttributeConverter ( https://hibernate.atlassian.net/browse/HHH-16671?atlOrigin=eyJpIjoiNzY4Nm... ) Thanks for the explanation. I may have been too hasty in reusing that other issue’s tests, sorry for that. What about the new @Type annotation? Is this supposed to work: @Id @Column(name = "year_month_key" ) @Type(YearMonthDateType.class) private YearMonth yearMonthKey; @Column(name = "year_month_value" ) @Type(YearMonthDateType.class) private YearMonth yearMonthValue; and then: entityManager.createQuery( "SELECT MAX(de.yearMonthKey) FROM DemoEntity de" ); entityManager.createQuery( "SELECT MAX(de.yearMonthValue) FROM DemoEntity de" ); ? I’m trying to migrate code that in 5.6 used: @TypeDefs({ @TypeDef(name = "yearmonth-date" , typeClass = YearMonthDateType.class, defaultForType = YearMonth.class), }) package pl.coretech.cdn.domain; import io.hypersistence.utils.hibernate.type.basic.YearMonthDateType; import org.hibernate.annotations.TypeDef; import org.hibernate.annotations.TypeDefs; import java.time.YearMonth; When I’m trying this on @Id column I get Could not create JdbcLiteralFormatter, UserType class [io.hypersistence.utils.hibernate.type.basic.YearMonthDateType] did not implement org.hibernate.usertype.EnhancedUserType , so this may be a Hypersistence issue, but what about that @Type on regular column? I’m attaching a test case with code above in case you want to look into this: test-case-2.zip ( https://hibernate.atlassian.net/rest/api/3/attachment/content/50421 ) ( https://hibernate.atlassian.net/browse/HHH-16671#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16671#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:da60ad2 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16671) Unable to query key attribute that uses AttributeConverter

by Piotr Przybylski (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16715) accept value() or element() in place of elements() and key() or index() in place of indices()

by Gavin King (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16715) accept value() or element() in place of elements() and key() or index() in place of indices()

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjA5YjAwNmZj... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiYjA5Yj... ) HHH-16715 ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiYjA5Yj... ) accept value() or element() in place of elements() and key() or index() in place of indices() ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiYjA5Yj... ) Change By: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Writing the docs, I _still_ struggle to explain the role of the {{elements()}} and {{indices()}} functions, and I think they’re still quite confusing. So what if we finally deprecated them and let you just use {{element()}}, {{value()}}, {{index()}}, and {{key()}} instead? That is, we would accept: # {{max(element(experiment.measurements))}}, {{max(index(record.revisions))}} # {{0.0 < every element(experiment.measurements)}}, {{1 = any index(record.revisions)}} # {{1 in index(record.revisions)}}, {{"hibernate" in element(document.tags)}} # {{exists(element(experiment.measurements))}} In case cases 1 and 4 , the revised syntax reads significantly better. In case 2, the revised syntax reads better if you use the {{every}} / {{any}} form of the quantifiers, or worse if you use the {{all}}/ {{some}} version. In case 3, the revised syntax reads definitely worse. But how useful is {{in}} with collections when we also have: * {{member of}} , and * the option of writing {{1 = any index(record.revisions)}}. Or perhaps we could just make {{elements}} a synonym for {{element}} and {{indices}} a synonym for {{index}} and let you write whatever you like. Thoughts? ( https://hibernate.atlassian.net/browse/HHH-16715#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16715#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:da60ad2 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16715) accept value() or element() in place of elements() and key() or index() in place of indices()

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=eyJpIjoiM2UyYjllZjhk... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiM2UyYj... ) HHH-16715 ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiM2UyYj... ) accept value() or element() in place of elements() and key() or index() in place of indices() ( https://hibernate.atlassian.net/browse/HHH-16715?atlOrigin=eyJpIjoiM2UyYj... ) Issue Type: Improvement Assignee: Unassigned Components: query-hql Created: 29/May/2023 12:44 PM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Writing the docs, I still struggle to explain the role of the elements() and indices() functions, and I think they’re still quite confusing. So what if we finally deprecated them and let you just use element() , value() , index() , and key() instead? That is, we would accept: * max(element(experiment.measurements)) , max(index(record.revisions)) * 0.0 < every element(experiment.measurements) , 1 = any index(record.revisions) * 1 in index(record.revisions) , "hibernate" in element(document.tags) In case 1, the revised syntax reads significantly better. In case 2, the revised syntax reads better if you use the every / any form of the quantifiers, or worse if you use the all / some version. In case 3, the revised syntax reads definitely worse. But how useful is in with collections when we also have: * member of , and * the option of writing 1 = any index(record.revisions). Or perhaps we could just make elements a synonym for element and indices a synonym for index and let you write whatever you like. Thoughts? ( https://hibernate.atlassian.net/browse/HHH-16715#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16715#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:da60ad2 )

2 years, 3 months

1
0
0 / 0

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

by Isaac Vásquez (JIRA)

Isaac Vásquez ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=627d288... ) *commented* on HHH-16697 ( https://hibernate.atlassian.net/browse/HHH-16697?atlOrigin=eyJpIjoiMjI0NW... ) Re: CALCULATED FIELDS in createNativeQuery doExtract integer insted of BigDecimals. ( https://hibernate.atlassian.net/browse/HHH-16697?atlOrigin=eyJpIjoiMjI0NW... ) OracleDialect.java resolveSqlTypeDescriptor :770 For some reason (that I don’t understand/know), *calculated fields* are getting ridded by scale 0, changing INTEGER, for FLOAT, is a it's a temporary patch, which requires more work to parse real integers/floats. ( 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:da60ad2 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16688) Some dirty attributes will not be updated for entities with superclasses

by Andrea Boriero (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-16688) Some dirty attributes will not be updated for entities with superclasses

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16688 ( https://hibernate.atlassian.net/browse/HHH-16688?atlOrigin=eyJpIjoiZmUzNz... ) Re: Some dirty attributes will not be updated for entities with superclasses ( https://hibernate.atlassian.net/browse/HHH-16688?atlOrigin=eyJpIjoiZmUzNz... ) Hi Georg Echterling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , I think this issue is the same as reported https://hibernate.atlassian.net/browse/HHH-16379 I’m going to close it. ( https://hibernate.atlassian.net/browse/HHH-16688#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16688#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:da60ad2 )

2 years, 3 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 May 2023