February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16238) Add support for mulitple generic embeddable properties in MappedSuperclass

by Marco Belladelli (JIRA)

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16238) Add support for mulitple generic embeddable properties in MappedSuperclass

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=eyJpIjoiNjNkZjg5YzQ5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16238?atlOrigin=eyJpIjoiNjNkZj... ) HHH-16238 ( https://hibernate.atlassian.net/browse/HHH-16238?atlOrigin=eyJpIjoiNjNkZj... ) Add support for mulitple generic embeddable properties in MappedSuperclass ( https://hibernate.atlassian.net/browse/HHH-16238?atlOrigin=eyJpIjoiNjNkZj... ) Issue Type: Bug Affects Versions: 6.2.0.CR2 Assignee: Unassigned Created: 28/Feb/2023 03:41 AM Priority: Major Reporter: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) At the moment an @Entity can extend a @MappedSuperclass which has two or more generic embeddable properties. This will work, but when trying to query the actual properties inside the *concrete* embeddable types (as opposed to the generic ones) an error will be thrown because we have no way of retrieving them. https://hibernate.atlassian.net/browse/HHH-16195 ( https://hibernate.atlassian.net/browse/HHH-16195 ) fixes embeddable-typed declaredProperties registration for generic embeddables on the superclass, and https://hibernate.atlassian.net/browse/HHH-16188 ( https://hibernate.atlassian.net/browse/HHH-16188 ) has prepared a foundation to register the actual concrete embeddable types that for now is only used for identifiers: * org.hibernate.metamodel.model.domain.AbstractManagedType.InFlightAccessImpl#applyGenericEmbeddableAttribute * org.hibernate.metamodel.model.domain.AbstractManagedType#findGenericEmbeddableAttribute This issue should address resolving concrete embeddable types for non-identifier properties. ( https://hibernate.atlassian.net/browse/HHH-16238#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16238#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#100217- sha1:65be9f2 )

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16237) versionUpdateGroup is null for Enity extending another Entity when only ElementCollection is updated.

by Joaquim Mascarenhas (JIRA)

Joaquim Mascarenhas ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTYyYWQ4Mjg3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16237?atlOrigin=eyJpIjoiYTYyYW... ) HHH-16237 ( https://hibernate.atlassian.net/browse/HHH-16237?atlOrigin=eyJpIjoiYTYyYW... ) versionUpdateGroup is null for Enity extending another Entity when only ElementCollection is updated. ( https://hibernate.atlassian.net/browse/HHH-16237?atlOrigin=eyJpIjoiYTYyYW... ) Issue Type: Bug Affects Versions: 6.2.0.CR2 Assignee: Unassigned Attachments: inheritance.zip Components: hibernate-core Created: 28/Feb/2023 03:35 AM Environment: Hibernate 6.2.0.CR2 Java 19 Priority: Major Reporter: Joaquim Mascarenhas ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) CustomCompany is an entity extending another entity Company. When I try to update only the ElementCollection in Company exception is thrown due to assertion error as versionUpdateGroup is null for Entity CustomCompany. UpdateCoordinatorStandard.doVersionUpdate(){ assert versionUpdateGroup != null; … } Please find attached test case. ( https://hibernate.atlassian.net/browse/HHH-16237#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16237#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#100217- sha1:65be9f2 )

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16236) Cannot use lists in where clause

by Svetliokapralov (JIRA)

Svetliokapralov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjIzMzkyMTVl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16236?atlOrigin=eyJpIjoiNjIzMz... ) HHH-16236 ( https://hibernate.atlassian.net/browse/HHH-16236?atlOrigin=eyJpIjoiNjIzMz... ) Cannot use lists in where clause ( https://hibernate.atlassian.net/browse/HHH-16236?atlOrigin=eyJpIjoiNjIzMz... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Components: hibernate-core Created: 28/Feb/2023 03:34 AM Priority: Major Reporter: Svetliokapralov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) This is a sample project demonstrating several Hibernate 6 problems related to using 'IN (:list)' in where clause: https://github.com/svkap/hibernate-6-bug-sample ( https://github.com/svkap/hibernate-6-bug-sample ) The project uses docker-compose for spinning up PostgreSQL + Flyway for db initialization. It uses spring-data and lombok. It seems there are problems when lists are used in queries and with coalesce. The Entities are fairly simple but have different column types. There are 3 different entity definition: 1. Using PostgreSQL enum + @Enumerated(EnumType.STRING) 2. Using varchar column + @Convert(...) 3. Using int column + @Convert(...) — The sample project tests several different queries and scenarios. Result summary: 1. Entity creation work for all scenarios. 2. Entity update work for all scenarios. 3. Return entity, use SpEl ( (:# {#list == null} = true) OR (i.list IN (:list)) ) works in JPQL 4. Pass Integer/String to native query works for coalesce and SpEl only when projection is returned — The exceptions seem the same when using PostgreSQL enum, Converter + String and Converter + Integer: 1. Return entity, native query + pass enums to repository method + ( (coalesce(:list, null) is null) OR (i.list IN (:list)) ) 1. java.lang.NullPointerException: Cannot invoke "org.hibernate.metamodel.mapping.JdbcMapping.getJdbcValueBinder()" because "jdbcMapping" is null 2. Return entity, native query + pass strings to repository method + ( (coalesce(:list, null) is null) OR (i.list IN (:list)) ) 1. org.springframework.dao.InvalidDataAccessResourceUsageException: Unable to find column position by name: id; SQL [n/a] 3. Return entity, native query + pass null to repository method + ( (coalesce(:list, null) is null) OR (i.list IN (:list)) ) 1. org.springframework.dao.InvalidDataAccessResourceUsageException: Unable to find column position by name: id; SQL [n/a] 4. Return entity, native query + pass enums to repository method + ( (:#{#list == null} = true) OR (i.list IN (:list)) ) 1. java.lang.NullPointerException: Cannot invoke "org.hibernate.metamodel.mapping.JdbcMapping.getJdbcValueBinder()" because "jdbcMapping" is null 5. Return entity, native query + pass null to repository method + ( (:# {#list == null} = true) OR (i.list IN (:list)) ) 1. org.springframework.dao.InvalidDataAccessResourceUsageException: Unable to find column position by name: id; SQL [n/a] 6. Return entity, native query + pass enum to repository method 1. java.lang.NullPointerException: Cannot invoke "org.hibernate.metamodel.mapping.JdbcMapping.getJdbcValueBinder()" because "jdbcMapping" is null 7. Return entity, native query + pass string to repository method + ( (:#{#list == null} = true) OR (i.list IN (:list)) ) 1. org.springframework.dao.InvalidDataAccessResourceUsageException: Unable to find column position by name: id; SQL [n/a] 7. Return entity, JPQL query + pass enum to repository method + ( (coalesce(:list, null) is null) OR (i.list IN (:list)) ) 1. java.lang.ClassCastException: class java.util.ImmutableCollections$List12 cannot be cast to class java.lang.Enum (java.util.ImmutableCollections$List12 and java.lang.Enum are in module java.base of loader 'bootstrap') 7. Return projection, native query + pass enum to repository method + ( (:# {#list == null} = true) OR (i.list IN (:list)) ) 1. java.lang.NullPointerException: Cannot invoke "org.hibernate.metamodel.mapping.JdbcMapping.getJdbcValueBinder()" because "jdbcMapping" is null ( https://hibernate.atlassian.net/browse/HHH-16236#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16236#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#100217- sha1:65be9f2 )

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16230) Wrong data in self-reference using L2C and BatchSize

by Andrea Boriero (JIRA)

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-15228) "round()" function in H2Dialect always returns Double as return type irrespective of argument.

by Søren Jepsen (JIRA)

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16219) Lazy loading of association involving loading of other, eager associations leads to unwanted loading beyond max_fetch_depth

by Yoann Rodière (JIRA)

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16219) Lazy loading of association involving loading of other, eager associations leads to unwanted loading beyond max_fetch_depth

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16219 ( https://hibernate.atlassian.net/browse/HHH-16219?atlOrigin=eyJpIjoiYzFlNT... ) Re: Lazy loading of association involving loading of other, eager associations leads to unwanted loading beyond max_fetch_depth ( https://hibernate.atlassian.net/browse/HHH-16219?atlOrigin=eyJpIjoiYzFlNT... ) Turns out that’s expected, and the model is to blame: https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/t... ( https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/t... ) > > > > Hi @Yoann Rodiere , looking at https://hibernate.atlassian.net/browse/HHH-16219 > ( https://hibernate.atlassian.net/browse/HHH-16219 ) , the test you > provided assumes that when you call entityB.getEntityA1() only entityA1 is > initialized but this is not correct, the call trigger also the > initialization of entityA2 so the different number of joins (to avoid this > entityA2 has to be annotated with @LazyGroup ). > The difference with Hibernate 5 is that now we execute only 1 queries to > initialize both entitA1 and entityA2 while in 5 we execute 2 queries one > for each association. > > ( https://hibernate.atlassian.net/browse/HHH-16219#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16219#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#100217- sha1:65be9f2 )

1 year, 2 months

1
0
0 / 0

[JIRA] (HHH-16230) Wrong data in self-reference using L2C and BatchSize

by Andrea Boriero (JIRA)

1 year, 2 months

1
0
0 / 0

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

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYzkxNmFm... ) / New Feature ( https://hibernate.atlassian.net/browse/HSEARCH-4574?atlOrigin=eyJpIjoiYzk... ) HSEARCH-4574 ( https://hibernate.atlassian.net/browse/HSEARCH-4574?atlOrigin=eyJpIjoiYzk... ) Explicit binding of constructor parameters for @ProjectionConstructor ( https://hibernate.atlassian.net/browse/HSEARCH-4574?atlOrigin=eyJpIjoiYzk... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Follows up on [https://hibernate.atlassian.net/browse/HSEARCH-3927|https://hibernate.atl...]. Use case: define a parameter of a projection constructor as a specific inner projection either something completely different from field projections such as an identifier projection, or more precise configuration of field value/object projections. For example: {code:java}@ProjectionConstructor record MyProjection(@IdProjection String id, @FieldProjection(convert = ValueConvert.NO) String myEnum){code} Currently, all constructor parameters are bound implicitly, which limits users to field projections or object projections. There is no ID projection in particular, which prevents from fully loading an entity through its projection constructor, since it can’t project on the ID. This also means {{-parameters}} _must_ be passed to the compiler when compiling projection constructors. Core set of annotations (must be implemented): * {{@IdProjection}} * {{@FieldProjection}} * {{@ObjectProjection}} ** we might want a {{includeDepth}} in here, * {{@ProjectionBinding(binder = ...)}} (for custom projection annotations) Less useful/more challenging annotations that could be split into another ticket: * {{@ScoreProjection}} * {{@DistanceProjection}} (=> moved to [https://hibernate.atlassian.net/browse/HSEARCH-4807|https://hibernate.atl...] ) * {{@EntityProjection}} * {{@EntityReferenceProjection}} * {{@DocumentReferenceProjection}} * Others, see all projections available. Some things to test in particular: * There should be no error if {{-parameters}} is not used when compiling, as long as all constructor parameters of a projection constructor have a {{@*Projection}} annotation (and that projection specifies the field path, if relevant). * There should be an error if {{-parameters}} is not used when compiling, and all constructor parameters of a projection constructor have a {{@*Projection}} annotation, but one of them is annotated with {{@FieldProjection}} or {{@ObjectProjection}} and does not specify the field path. * There should be an error when using two {{@*Projection}} annotations on the same constructor parameter. * And more (the list above is not exhaustive, obviously). ( https://hibernate.atlassian.net/browse/HSEARCH-4574#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4574#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#100217- sha1:65be9f2 )

1 year, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2023