February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Tomas Cerskus (JIRA)

Tomas Cerskus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) *commented* on HHH-16136 ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiNDMxNT... ) Re: LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiNDMxNT... ) So from what I understand now, is that if proxies may be involved, users should always use getters and should not access the fields directly. I will update the test case and the issue title, to make it clear there’s only an bug when bytecode enhancement is turned on. ( https://hibernate.atlassian.net/browse/HHH-16136#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16136#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:6795dbd )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16151) NPE SqmTreePrinter.visitLikePredicate getEscapeCharacter is null

by Jan Schatteman (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Tomas Cerskus (JIRA)

Tomas Cerskus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) *commented* on HHH-16136 ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiOGFmM2... ) Re: LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiOGFmM2... ) Hey @Marco Belladelli, thanks for investigating this. Great to hear that there is a work-around! I just checked myself and without the bytecode enhancement turned on, it does indeed make the tests pass. I you turn on the enchacement (uncomment the annotation above the test class) - it fails even with order.getUser().getName() ( https://hibernate.atlassian.net/browse/HHH-16136#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16136#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:6795dbd )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16094) CLOB validation with MySQL wrongly fails when different clob type is used than expected

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16094 ( https://hibernate.atlassian.net/browse/HHH-16094?atlOrigin=eyJpIjoiNGZlOT... ) Re: CLOB validation with MySQL wrongly fails when different clob type is used than expected ( https://hibernate.atlassian.net/browse/HHH-16094?atlOrigin=eyJpIjoiNGZlOT... ) Hello, this issue seems to be caused by the MySQL driver reporting LONGTEXT columns with type code Types.LONGVARCHAR (-1), whereas Hibernate is expecting a Types.CLOB (2005). A possible workaround is forcing Hibernate to consider the name property of type LONGTEXT by e.g. setting the column length to a value that would require that type (> 16,777,215). ( https://hibernate.atlassian.net/browse/HHH-16094#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16094#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:6795dbd )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16119) Named native queries do not work with jakarta.persistence.Tuple result class

by Andrea Boriero (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4774) Database deadlock while processing events with MS SQL Server

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4774 ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiZmZ... ) Re: Database deadlock while processing events with MS SQL Server ( https://hibernate.atlassian.net/browse/HSEARCH-4774?atlOrigin=eyJpIjoiZmZ... ) I managed to reproduce the problem locally and reliably using these commands: mvn clean install -DskipTests mvn docker:start -Pci-mssql -pl build/parents/integrationtest -Dtest.database.run.mssql.skip=false i=0; while mvn verify -f integrationtest/mapper/orm-coordination-outbox-polling -Dit.test='Outbox*Concurrency*' -Dtest.database.run.skip=true -P ci-mssql -Dtest.launcher.args='-XX:ActiveProcessorCount=2' 1>/dev/null 2>&1 ; do (( i ++ )); echo "Succeeded; trying again ($i)..."; done ; echo 'Failed!' It generally takes less than 4 attempts to reproduce the problem on my machine. ( https://hibernate.atlassian.net/browse/HSEARCH-4774#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4774#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#100214- sha1:6795dbd )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16136) LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16136 ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiZTc1ZD... ) Re: LAZY @ManyToOne may break EAGER @ManyToOne when used on the same entity in a different parent ( https://hibernate.atlassian.net/browse/HHH-16136?atlOrigin=eyJpIjoiZTc1ZD... ) Hello Tomas Cerskus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f3fc10... ) , thanks for reporting the issue! I ran some tests with you reproducer and I can say that the problem only occurs when accessing fields with the dot notation (e.g. order.user.id ) but it doesn’t happen when using getter methods ( order.getUser().getId() ). This is due to how Hibernate fetches and initializes associated entities. With version 5 it only worked for this particular case because the order of initialization for associated entities was different and order.user was not a HibernateProxy , but this is purely by chance (different property names / JVM could change this behavior). Even in Hibernate 5, if you try setting the association to LAZY and manually initializing the user property (calling for example order.getUser().getName() ), you will see that accessing the field with the dot notation still yields null , but using getter methods the values are correct. Using getter methods for properties should solve all issues. Let me know if I can help you with anything else. ( https://hibernate.atlassian.net/browse/HHH-16136#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16136#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:6795dbd )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16151) NPE SqmTreePrinter.visitLikePredicate getEscapeCharacter is null

by Daniel Stroh (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16151) NPE SqmTreePrinter.visitLikePredicate getEscapeCharacter is null

by Daniel Stroh (JIRA)

Daniel Stroh ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63e36f3... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiN2ViYjMxNzE1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16151?atlOrigin=eyJpIjoiN2ViYj... ) HHH-16151 ( https://hibernate.atlassian.net/browse/HHH-16151?atlOrigin=eyJpIjoiN2ViYj... ) NPE SqmTreePrinter.visitLikePredicate getEscapeCharacter is null ( https://hibernate.atlassian.net/browse/HHH-16151?atlOrigin=eyJpIjoiN2ViYj... ) Issue Type: Bug Affects Versions: 6.1.6 Assignee: Unassigned Components: query-hql Created: 08/Feb/2023 02:09 AM Environment: 6.1.5 Hibernate, Java 10, macOS Venture 13.1, Postgres 14.6 Priority: Minor Reporter: Daniel Stroh ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63e36f3... ) @Entity public class Test { @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "id" , nullable = false ) private Long id; private String x; public Long getId() { return id; } public void setId( Long id) { this.id = id; } public String getX() { return x; } public void setX( String x) { this.x = x; } } @Repository public interface TestRepository extends CrudRepository<Test, Long > { @Transactional @Modifying @Query(value = "UPDATE Test t SET t.x = :value1 " + "WHERE t.x LIKE :value2" ) void update( String value1, String value2); } during startup with logging.level.org.hibernate: TRACE logging SqmTreePrinter.visitLikePredicate results in an NPE because predicate.getEscapeCharacter() is null. I am not sure what the escape character should look like of a predicate, but can’t we just check if the escape character is not null? low priority because it is just a logging issue ( https://hibernate.atlassian.net/browse/HHH-16151#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16151#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:6795dbd )

2 years, 10 months

1
0
0 / 0

[JIRA] (HBX-2479) Update version identifier to 6.2.0-SNAPSHOT

by Koen Aers (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