August 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13170) GORM: Challenges migrating away from deprecated Criteria API

by Eduardo Simioni (JIRA)

Eduardo Simioni ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13170 ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiNjA5YT... ) Re: GORM: Challenges migrating away from deprecated Criteria API ( https://hibernate.atlassian.net/browse/HHH-13170?atlOrigin=eyJpIjoiNjA5YT... ) What about the criteria.add(Restrictions.sqlRestriction()) option? I’ve started a branch to migrate my company’s code to Hibernate 6 (Hibernate Criteria to JPA basically), but I can’t complete this migration without an sql restriction alternative. We are using only criteria, no HQL. I’ve got very far and thought of possible alternative solutions, but in the end, although we have just 31 usages in a very large project, I could only migrate a few of them to other solutions, for all the rest, a replacement to SQL Restriction is absolutely needed. ( https://hibernate.atlassian.net/browse/HHH-13170#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13170#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#100204- sha1:f005d5a )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expression results in UnsupportedOperationException

by Hernan (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15452) Predicate add expresion results in UnsupportedOperationException

by Hernan (JIRA)

Hernan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fba63... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmZkMWJlYzcw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiZmZkMW... ) HHH-15452 ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiZmZkMW... ) Predicate add expresion results in UnsupportedOperationException ( https://hibernate.atlassian.net/browse/HHH-15452?atlOrigin=eyJpIjoiZmZkMW... ) Issue Type: Bug Affects Versions: 6.1.1 Assignee: Unassigned Components: hibernate-core Created: 16/Aug/2022 07:55 AM Environment: Hibernate ORM core version 6.1.1.Final, openjdk version "11" 2018-09-25, Ubuntu 20.04.4 LTS, SQL Server 2008 R2 (SP3) Priority: Major Reporter: Hernan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fba63... ) While upgrating Hibernate version from 4.3.7 to 6.1.1 I'm getting an Exception running a piece of code that used to work and is found in several tutorials and examples The simplest code I can build to show the behavior is: CriteriaBuilder builder = em4.getCriteriaBuilder(); CriteriaQuery<Persona> cq = builder.createQuery(Persona.class); Root<Persona> rootClaseGrid = cq.from(Persona.class); cq.select(rootClaseGrid); Predicate conjuncion = builder.conjunction(); Predicate expr = builder.equal(rootClaseGrid.get( "documento" ), "AAAA" ); conjuncion.getExpressions().add(expr); Last line throws: Exception in thread "main" java.lang.UnsupportedOperationException at java.base/java.util.AbstractList.add(AbstractList.java:153) at java.base/java.util.AbstractList.add(AbstractList.java:111) at pruebas.PruebaHM.main(PruebaHM.java:181) Debugging Hibernate code shows that method "getExpressions" resolves in class "org.hibernate.query.sqm.tree.predicate.AbstractSqmPredicate", with code: @Override public List<Expression< Boolean >> getExpressions() { /// most predicates do not have sub-predicates return Collections.emptyList(); } in fact returning always an emptyList of java.util.AbstractList, trying to add elements always throws UnsupportedOperationException: public void add( int index, E element) { throw new UnsupportedOperationException(); } Older versions (for instance 4.3.7) manage a list of Expression<Boolean>, the last line in the code above resolves in class "org.hibernate.jpa.criteria.predicate.CompoundPredicate" : @Override public List<Expression< Boolean >> getExpressions() { return expressions; } Thanks in advance ( https://hibernate.atlassian.net/browse/HHH-15452#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15452#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#100204- sha1:f005d5a )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15451) Upgrade PostgreSQL JDBC driver to 42.4.1

by Sanne Grinovero (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15449) @ManyToOne associations not loaded correctly with default EAGER and batch fetch property set when using TypedQuery.resultStream

by Andrea Boriero (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15450) Add fluent style access type

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15450 ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNTc2NG... ) Re: Add fluent style access type ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNTc2NG... ) We might want to consider how to make that the default, as well. We could have a configuration property (“use the FLUENT access type instead of PROPERTY by default” = true, “). We could also try to emulate the current mechanism based on @Id : on an entity, if the @Id annotation is found on a method that doesn’t follow the JavaBeans naming conventions (e.g. Long id() ), then we would default to the FLUENT access type. There are multiple challenges, though: * No idea how this would work on mapped superclasses that don’t include an ID, but I suspect we have the same problem with the current access type (no way to decide on a default). * What if I have a property in the fluent style that happens to also match JavaBeans conventions, e.g.`getDoneFast`? ( boolean getDoneFast; public boolean getDoneFast(); public boolean getDoneFast(boolean value); ) ( https://hibernate.atlassian.net/browse/HHH-15450#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15450#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#100204- sha1:f005d5a )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15440) @OneToOne and @OptimisticLock(excluded = true) not working correctly

by Andrea Boriero (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-15450) Add fluent style access type

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGJhZGZjNWVi... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) HHH-15450 ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) Add fluent style access type ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 16/Aug/2022 05:54 AM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The “fluent” style is to not have prefixes for method names. Every no-arg non-void method is considered a property. A single arg void method with the same name and argument type matching the read accessor type, is considered to be the write accessor. For example: @Entity @Access(FLUENT) public class Blog { ... public String title() {...} public void title( String title) {...} } It might be worth considering same named single argument methods also as write accessors, regardless of the return type, to support use cases where the write accessor returns the “this” object for chained method invocation. ( https://hibernate.atlassian.net/browse/HHH-15450#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15450#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#100204- sha1:f005d5a )

2 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-4500) Provide more context in error messages about fields with invalid type (value vs. object)

by Yoann Rodière (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-4656) Provide more guidance in error messages when calling "retrieve-by-name" methods

by Yoann Rodière (JIRA)

2 years, 4 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 August 2022