October 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-15593) Illegal Update-Statement generated

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15593 ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiYmJlOD... ) Re: Illegal Update-Statement generated ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiYmJlOD... ) You can read the documentation section on the @NotFound annotation which explains why implicit joins like sender.id are treated this way: https://docs.jboss.org/hibernate/orm/5.6/userguide/html_single/Hibernate_... ( https://docs.jboss.org/hibernate/orm/5.6/userguide/html_single/Hibernate_... ) ( https://hibernate.atlassian.net/browse/HHH-15593#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15593#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15593) Illegal Update-Statement generated

by Wolfgang Klaus (JIRA)

Wolfgang Klaus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15593 ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiYzk3OT... ) Re: Illegal Update-Statement generated ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiYzk3OT... ) Thank you for the clarification. What is the background of this breaking change? I only want to unterstand it. ( https://hibernate.atlassian.net/browse/HHH-15593#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15593#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15593) Illegal Update-Statement generated

by Christian Beikov (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15593) Illegal Update-Statement generated

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15593 ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiODAyNz... ) Re: Illegal Update-Statement generated ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiODAyNz... ) I understand that this is unfortunate, but I doubt that you want the semantically correct query: update NACHRICHT set titel= 'abc' where LID=( select N.LID from NACHRICHT N join PORTALNUTZER PN on N.LSENDERID=PN.LID where PN.LID=? ) You will just have to switch to the fk function if you want to access the foreign key column of an association that has a NotFoundAction specified. ( https://hibernate.atlassian.net/browse/HHH-15593#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15593#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15593) Illegal Update-Statement generated

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15593 ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiMmNjYz... ) Re: Illegal Update-Statement generated ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiMmNjYz... ) This is due to your use of not-found=”ignore” for your many-to-one which tells Hibernate, that the value in the LSENDERID column might not point to an actual row in the PORTALNUTZER table. Either remove the not-found attribute or change your query to... where fk(sender) = :pnutzerid. ( https://hibernate.atlassian.net/browse/HHH-15593#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15593#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-13338) "Unique Index Violation" when removing element on OneToMany children list with OrderColumn

by Burkhard Graves (JIRA)

Burkhard Graves ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13338 ( https://hibernate.atlassian.net/browse/HHH-13338?atlOrigin=eyJpIjoiYzNiNj... ) Re: "Unique Index Violation" when removing element on OneToMany children list with OrderColumn ( https://hibernate.atlassian.net/browse/HHH-13338?atlOrigin=eyJpIjoiYzNiNj... ) [can it be that mentioning with @ does not work or am I just too stupid? 😉] @Carsten Otto, your reproducer succeeds if you annotate your test with @Transactional - but it also should work without it, I think. Maybe I should have included this problem in https://hibernate.atlassian.net/browse/HHH-15591 ( https://hibernate.atlassian.net/browse/HHH-15591 ) … ( https://hibernate.atlassian.net/browse/HHH-13338#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13338#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15059) Pre-collection remove envers event listener leads to OOM

by Ivaylo Mitrev (JIRA)

Ivaylo Mitrev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15059 ( https://hibernate.atlassian.net/browse/HHH-15059?atlOrigin=eyJpIjoiNWYyOG... ) Re: Pre-collection remove envers event listener leads to OOM ( https://hibernate.atlassian.net/browse/HHH-15059?atlOrigin=eyJpIjoiNWYyOG... ) Hey! Just wanted to see if you are planning any changes related to this in the near future? ( https://hibernate.atlassian.net/browse/HHH-15059#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15059#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-4715) Simplify Maven profiles and groups for Elasticsearch testing

by Yoann Rodière (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-4715) Simplify Maven profiles and groups for Elasticsearch testing

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMTI4MDAz... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4715?atlOrigin=eyJpIjoiMTI... ) HSEARCH-4715 ( https://hibernate.atlassian.net/browse/HSEARCH-4715?atlOrigin=eyJpIjoiMTI... ) Simplify Maven profiles and groups for Elasticsearch testing ( https://hibernate.atlassian.net/browse/HSEARCH-4715?atlOrigin=eyJpIjoiMTI... ) Issue Type: Task Assignee: Unassigned Components: build, integration, tests Created: 11/Oct/2022 00:23 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Elasticsearch testing is set up this way: * In the Jenkinsfile, we enable a profile (e.g. elasticsearch-6.0) * In Maven, in the parent POM for integration tests, that profile defines what we will be testing against ( https://github.com/hibernate/hibernate-search/blob/aaa193330ced3a5858daa0... ) : the distribution ( elastic ) and the exact version (e.g. 6.2.4 ), as well as the container image (OpenSearch vs. Elastic, via test.elasticsearch.run.elastic.skip / test.elasticsearch.run.opensearch.skip ). * In Maven, in the parent POM for integration tests, that profile used to set up “test dialects” ( https://github.com/hibernate/hibernate-search/blob/aaa193330ced3a5858daa0... ) , but that’s no longer the case after https://hibernate.atlassian.net/browse/HSEARCH-4705 ( https://hibernate.atlassian.net/browse/HSEARCH-4705 ). * In Maven, in the POM of specific integration tests, that profile defines excluded JUnit Categories ( https://github.com/hibernate/hibernate-search/blob/37629846de5d1ccd1ffd99... ) , so that we don’t execute some tests that are irrelevant for that version. This is all quite complicated, so I think we should try to do better: * In the Jenkinsfile, we set the full distribution and version explicitly, not a profile. I.e. we use -Dtest.elasticsearch.connection.distribution=... -Dtest.elasticsearch.connection.version=... For AWS, we will have to provide an approximation of the version that we expect to run on the AWS Service. * In Maven, in the parent POM for integration tests, we enable one of two profiles ( opensearch / elastic ) according to the distribution that was set explicitly, just to define the container image (OpenSearch vs. Elastic, via test.elasticsearch.run.elastic.skip / test.elasticsearch.run.opensearch.skip ). * For tests that cannot run against all versions, instead of using JUnit Categories, we will just use assume and test the actual version of Elasticsearch, like we do in TCK tests with ElasticsearchTckBackendFeatures. Later when we switch to JUnit 5 ( https://hibernate.atlassian.net/browse/HSEARCH-3654 ( https://hibernate.atlassian.net/browse/HSEARCH-3654 ) ), we might be able to improve on that and simply rely on annotations; but we’re not there yet. Advantages: * It’s simpler * It’s more versatile: you can more easily test any version of Elasticsearch/OpenSearch. * It’s clearer: instead of displaying a version range on CI, we can display the exact version we expect to run against. Additionally, we may be able to simplify the -Dtest.elasticsearch.connection.distribution=elastic -Dtest.elasticsearch.connection.version=7.10.2 to just -Dtest.elasticsearch.version=elastic:7.10.2 ; but that will only be possible if we can enable profiles based on patterns ( elastic: ** */ opensearch:* ). I’m not sure that’s possible. Maybe a middleground would be to remove.connection from the property names. ( https://hibernate.atlassian.net/browse/HSEARCH-4715#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4715#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#100208- sha1:38b2e23 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15593) Illegal Update-Statement generated

by Wolfgang Klaus (JIRA)

Wolfgang Klaus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZGE5YzIwZGNk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiZGE5Yz... ) HHH-15593 ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiZGE5Yz... ) Illegal Update-Statement generated ( https://hibernate.atlassian.net/browse/HHH-15593?atlOrigin=eyJpIjoiZGE5Yz... ) Issue Type: Bug Affects Versions: 5.3.21, 5.6.12 Assignee: Unassigned Attachments: hbex.zip Components: hibernate-core Created: 11/Oct/2022 00:20 AM Environment: hibernate-orm: 5.3.21 JVM: OpenJDK Runtime Environment (build 1.8.0_232-b09) OS: Microsoft Windows \[Version 10.0.19042.2006] Database: HSQL Priority: Major Reporter: Wolfgang Klaus ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The following Entities are given <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"><hibernate-mapping> <class dynamic-insert="false" dynamic-update="true" name="org.example.Nachricht" table="NACHRICHT"> <id column="LID" name="id" type="java.lang.Long" unsaved-value="-1"> <generator class="increment"> </generator> </id> <property column="titel" insert="true" name="titel" not-null="true" type="java.lang.String" update="true"/> <many-to-one class="org.example.Portalnutzer" column="LSENDERID" name="sender" not-found="ignore" not-null="false"/> </class> </hibernate-mapping> <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"><hibernate-mapping> <class dynamic-insert="false" dynamic-update="true" name="org.example.Portalnutzer" optimistic-lock="version" table="PORTALNUZTER"> <id column="LID" name="id" type="java.lang.Long" unsaved-value="-1"> <generator class="increment"> </generator> </id> <property column="name" insert="true" name="titel" not-null="true" type="java.lang.String" update="true"/> <set cascade="save-update" inverse="true" name="gesendeteNachrichten"> <key column="LSENDERID"/> <one-to-many class="org.example.Nachricht"/> </set> </class> </hibernate-mapping> Until Version 5.3.20.Final the following HQL-Statement generates a correct SQL-Update-Statement session.createQuery("update Nachricht set titel='abc' where sender.id=:pnutzerid "); Correct generated SQL-Statement is: update NACHRICHT set titel='abc' where LSENDERID=? After Upgrading to version 5.3.21.Final the same HQL generates the following wrong SQL-Statement update NACHRICHT cross join set titel='abc' where LID=? Has this change been made deliberately or is it a bug? A complete example to reproduce the error is attached. Change the hibernate-Version in the pom.xml ( https://hibernate.atlassian.net/browse/HHH-15593#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15593#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#100208- sha1:38b2e23 )

2 years, 3 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 October 2022