May 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16572) Bad enhancement for PROPERTY attributes with mismatched field and method names

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16572) jpa/core/query/flushmode TCK test failures

by Steve Ebersole (JIRA)

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiY2U4Yj... ) Re: jpa/core/query/flushmode TCK test failures ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiY2U4Yj... ) > > > > I remember porting this from the Javassist implementation back in the > days, I can hardly imagine that I came up with this approach. > > The older Javassist enhancer had the same problem when we checked. > > > > The decision to place this field name is made here: https://github.com/hibernate/hibernate-orm/blob/2d345fc04bf4c2df1d76d5f89... > > > That’s one place. It is a problem in many of the places persistentField.getName() is used. > > > > Is the required information available at this point? > > Unfortunately not. Largely this boils down to being able to understand the jakarta.persistence.AccessType in effect for each attribute, which is not a simple determination as we have to look across all fields and methods of the class and its supers. We have code that does this of course, but it is all based on the Class and reflection. And for enhancement, I’m not sure we always have access to all classes when enhancing one. ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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:55ea0c5 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16542) Bad get/is handling with bytecode enhancement

by Steve Ebersole (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Jan Schatteman (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16580) Some typos in org.hibernate.query.sqm

by Jan Schatteman (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16582) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16581) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjQ1NzBkMDdk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYjQ1Nz... ) HHH-16581 ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYjQ1Nz... ) in 6.2 I start getting Multiple '@FilterDef' annotations define a filter named error on startup ( https://hibernate.atlassian.net/browse/HHH-16581?atlOrigin=eyJpIjoiYjQ1Nz... ) Issue Type: Bug Assignee: Unassigned Created: 10/May/2023 08:38 AM Environment: Seems there is a change that breaks backward compatibility... I have some entity classes preprocessing that dynamically adds filter defs annotation based on some conditions So it can happen that entity A will have filterDefs filterA and FilterB and entity B will have filterDef filterA It was working in hibernate version 3-5 and in 6.1.7 in 6.2.2 it gives me an error. Can you please revert that condition or outline a context for filterDefs is it class(seems not), package, persistent unit ? I have 4 persistent units.. and a single instance of class transformer that intercepts class loading and it doesn't know anything about persistent unit that class belongs :( And maybe update docs as I didn't find any information about this requirement and some motivation of why it was added Priority: Major Reporter: Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) ( https://hibernate.atlassian.net/browse/HHH-16581#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16581#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:55ea0c5 )

2 years, 11 months

1
0
0 / 0

[JIRA] (BVAL-787) Alias XXX used for multiple from-clause elements error when executing query with 2 level join

by Oleksii Miroshnyk (JIRA)

Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) *created* an issue Bean Validation ( https://hibernate.atlassian.net/browse/BVAL?atlOrigin=eyJpIjoiY2E1NjljMmZ... ) / Bug ( https://hibernate.atlassian.net/browse/BVAL-787?atlOrigin=eyJpIjoiY2E1Njl... ) BVAL-787 ( https://hibernate.atlassian.net/browse/BVAL-787?atlOrigin=eyJpIjoiY2E1Njl... ) Alias XXX used for multiple from-clause elements error when executing query with 2 level join ( https://hibernate.atlassian.net/browse/BVAL-787?atlOrigin=eyJpIjoiY2E1Njl... ) Issue Type: Bug Assignee: Unassigned Created: 10/May/2023 08:22 AM Environment: java 17, spring boot 3, hibernate 6.1.7 Priority: Blocker Reporter: Oleksii Miroshnyk ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5a157d9... ) Seems there is a bug somewhere either in query parsing or joins processing in hibernate 6.1.7+ That code & query works fine in all prev. versions from hibernate 3 to 5 I have a named query: ``` <query>SELECT COUNT(adminPermission) FROM org.broadleafcommerce.openadmin.server.security.domain.AdminPermission adminPermission LEFT OUTER JOIN adminPermission.allChildPermissions childPermission LEFT OUTER JOIN childPermission.qualifiedEntities childQualifiedEntity LEFT OUTER JOIN adminPermission.qualifiedEntities qualifiedEntity LEFT OUTER JOIN adminPermission.allRoles role LEFT OUTER JOIN role.allUsers roleUser LEFT OUTER JOIN adminPermission.allUsers permissionUser WHERE (roleUser = :adminUser OR permissionUser = :adminUser) AND (adminPermission.type = :type OR adminPermission.type = 'ALL' OR childPermission.type = :type OR childPermission.type = 'ALL') AND (qualifiedEntity.ceilingEntityFullyQualifiedName = :ceilingEntity OR childQualifiedEntity.ceilingEntityFullyQualifiedName = :ceilingEntity) </query> ``` There OneToMany and ManyToMany through JoinTable asossiations it this is important I debugged a bit and see that it processes condition (roleUser = :adminUser OR permissionUser = :adminUser) and finds a join LEFT OUTER JOIN role.allUsers roleUser so it finds alias "roleUser", logic goes into org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#visitSetJoin where it does: final SqmSetJoin copy = new SqmSetJoin<>( findSqmFromCopy( join.getLhs() ), so join.getLhs() will return another join LEFT OUTER JOIN adminPermission.allRoles role so it finds alias "role" And in org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#findSqmFromCopy it does return (X) sqmFrom.accept( this ); So it will do a recursive call that will eventually come to org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#visitSetJoin again, where it will process join with alias "role" and in org.hibernate.query.hql.internal.QuerySplitter.UnmappedPolymorphismReplacer#visitJoins will register that alias, and also it will do join.visitSqmJoins( sqmJoin -> sqmJoin.accept( this ) ); where "role" join will reference "roleUser" join via joins.forEach( consumer ); in org.hibernate.query.sqm.tree.domain.AbstractSqmFrom#visitSqmJoins it will process it and also registers via org.hibernate.query.hql.internal.SqmPathRegistryImpl#register(org.hibernate.query.sqm.tree.domain.SqmPath<?>) so now registry map knows about "role" and "roleUser" joins and recursion ends and it eventually continues to process "roleUse" join - where we start recursion... and it again will attempt to register org.hibernate.query.hql.internal.SqmPathRegistryImpl#register(org.hibernate.query.sqm.tree.domain.SqmPath<?>) where it fails with exception... So there is something wrong on how "multi-level joins" are handled. ( https://hibernate.atlassian.net/browse/BVAL-787#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/BVAL-787#add-comment?atlOrigin=eyJ... ) 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:55ea0c5 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HHH-16498) Hibernate DDL validation fails on enum database column type

by Čedomir Igaly (JIRA)

Čedomir Igaly ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16498 ( https://hibernate.atlassian.net/browse/HHH-16498?atlOrigin=eyJpIjoiYjJlOT... ) Re: Hibernate DDL validation fails on enum database column type ( https://hibernate.atlassian.net/browse/HHH-16498?atlOrigin=eyJpIjoiYjJlOT... ) Fix for 6.2 - pull request 6541 ( https://github.com/hibernate/hibernate-orm/pull/6541 ) ( https://hibernate.atlassian.net/browse/HHH-16498#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16498#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:55ea0c5 )

2 years, 11 months

1
0
0 / 0

[JIRA] (HV-1847) Method Constraints declared on interfaces are not being validated unless implementation contains validation annotations

by Guillaume Smet (JIRA)

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