February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-15802) SubQuery with "in" results in java.lang.ClassCastException: class org.hibernate.metamodel.mapping.internal.BasicEntityIdentifierMappingImpl cannot be cast to class org.hibernate.metamodel.mapping.EntityValuedModelPart

by Andrea Boriero (JIRA)

2 years, 10 months

1
0
0 / 0

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

by Andrea Boriero (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15664) Documentation states that native database array types are unsupported

by Andrea Boriero (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Markus Heiden (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Alexander Savov (JIRA)

Alexander Savov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNDhlND... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNDhlND... ) Markus, thank you so much for the investigation. Really hope that someone from Hibernate team will confirm and share what’s the plan for the fix. I came up with some sort of partial fix moving all the props from the Generic class to “artificially“ introduced parent class that is NOT generic. However for the Generic property that’s not an option. @MappedSuperclass public static class TaskServiceDocumentFix extends MultiTenantDocument { // Now this prop is part of the parent non-generic class and is OK @Type(JsonBinaryType.class) @Column(columnDefinition = "jsonb") public ServiceTaskCallback serviceTaskCallback; } @MappedSuperclass public static class TaskServiceDocument<E extends Enum<E>> extends TaskServiceDocumentFix { // However this does not work @Enumerated(EnumType.STRING) public E taskSubStage; } ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Markus Heiden (JIRA)

Markus Heiden ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6149cfc... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNWNlM2... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNWNlM2... ) The problem seems to be org.hibernate.boot.model.internal.ClassPropertyHolder#addPropertyToMappedSuperclass which handles parameterized superclasses differently from non-parameterized superclasses. For non-parameterized superclasses, it just adds the property. For parameterized superclasses, it does some “magic”. In this case if ( inferredData.getTypeName().equals( getTypeName( originalValue ) ) ) seems to be the problem, because originalValue does not yet have its typeName set and thus the if-condition evaluates to false instead of adding the property and return. ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:4a69e91 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16149) @Immutable for @Embeddable

by Steve Ebersole (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16145) @Mutability for @Embeddable

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=eyJpIjoiYjc3MDk1OTlm... ) / Sub-task ( https://hibernate.atlassian.net/browse/HHH-16145?atlOrigin=eyJpIjoiYjc3MD... ) HHH-16145 ( https://hibernate.atlassian.net/browse/HHH-16145?atlOrigin=eyJpIjoiYjc3MD... ) @Mutability for @Embeddable ( https://hibernate.atlassian.net/browse/HHH-16145?atlOrigin=eyJpIjoiYjc3MD... ) Change By: Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) We Should we allow {{@ Immutable Mutability }} on an entity and on an embeddable. Should we allow {{@ Mutability Embeddable }} in those targets as well ? If so, what is the semantic? Does NOTE: not considering it transitively apply the {{MutabilityPlan}} to all of the managed-type’s attributes? Or does it apply just to the managed-type itself? Not sure that {{MutabilityPlan}} applied just to the for entity makes sense. as Hibernate has very specific needs for the {{MutabilityPlan}} related to an entity for proper caching behavior, etc. ( https://hibernate.atlassian.net/browse/HHH-16145#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16145#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:4a69e91 )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16145) @Mutability for @Embeddable

by Steve Ebersole (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16148) Introduce Immutability (MutabilityPlan) for use with @Mutability

by Steve Ebersole (JIRA)

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