August 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-14152) Query fails after upgrading to 5.4.20.Final

by Scott Roehrig (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14152) Query fails after upgrading to 5.4.20.Final

by Scott Roehrig (JIRA)

Scott Roehrig ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14152 ( https://hibernate.atlassian.net/browse/HHH-14152?atlOrigin=eyJpIjoiNTYyMj... ) Re: Query fails after upgrading to 5.4.20.Final ( https://hibernate.atlassian.net/browse/HHH-14152?atlOrigin=eyJpIjoiNTYyMj... ) As far as a test case, I provided the sql scripts in use, but it should be possible to potentially reproduce this. I am attaching the updated file set that seems to work. ( https://hibernate.atlassian.net/browse/HHH-14152#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14152#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14152) Query fails after upgrading to 5.4.20.Final

by Scott Roehrig (JIRA)

Scott Roehrig ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14152 ( https://hibernate.atlassian.net/browse/HHH-14152?atlOrigin=eyJpIjoiMjQ1YW... ) Re: Query fails after upgrading to 5.4.20.Final ( https://hibernate.atlassian.net/browse/HHH-14152?atlOrigin=eyJpIjoiMjQ1YW... ) The issue appears to be in the mutli line parsing for the load script under HSQLDB. If the file is reformatted to use single line inserts only, it appears to be functioning properly. Once multi lines are inserted it fails in the database creation from persistence.xml. As I believe there may have been changes in this area under https://hibernate.atlassian.net/browse/HHH-14033 that were backported into 5.4.20, it might be that has caused a regression. ( https://hibernate.atlassian.net/browse/HHH-14152#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14152#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14152) Query fails after upgrading to 5.4.20.Final

by Scott Roehrig (JIRA)

Scott Roehrig ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14152 ( https://hibernate.atlassian.net/browse/HHH-14152?atlOrigin=eyJpIjoiY2Q3Nm... ) Re: Query fails after upgrading to 5.4.20.Final ( https://hibernate.atlassian.net/browse/HHH-14152?atlOrigin=eyJpIjoiY2Q3Nm... ) Providing the source isn’t possible as it is commercially licensed code. I have been able to debug this further and I may have narrowed the issue down. I wrote a second test case as follows: final EntityManager manager = com.gemalto.ics.usplatform.bip.persistence.EntityManagerFactory.newInstance().createEntityManager(); {{try { }} Query query = manager.createNativeQuery("SELECT IDENTIFIER FROM ISSUERS WHERE ISSUER = 1 AND IDENTIFIER = '1'"); query.setHint(QueryImpl.QUERY_HINT_READ_ONLY, true); List<Object> results = query.getResultList(); query = manager.createNativeQuery("SELECT IDENTIFIER FROM RESOURCES WHERE ISSUER = 1 AND IDENTIFIER = '1'"); query.setHint(QueryImpl.QUERY_HINT_READ_ONLY, true); results = query.getResultList(); query = manager.createQuery( "SELECT DISTINCT resource FROM IssuerImpl resource WHERE resource.identifier = :identifier"); query.setParameter("identifier", new com.gemalto.ics.usplatform.bip.IdentifierImpl(1L, "1")); query.setHint(QueryImpl.QUERY_HINT_READ_ONLY, true); results = query.getResultList(); {{} finally { manager.close();} }} What I found is interesting. The FIRST query which looks at the CHILD table ISSUERS finds the ROW in 5.4.19/5.4.20. BUT, in 5.4.20 the parent table RESOURCES is missing the row while it is not missing the row in 5.4.19. This only happens when the persistence.xml is configured to create the tables and structure at runtime (in unit tests for instance). The structure is created via a create.sql and a load.sql. In 5.4.19 that function works correctly and the tables have the proper entries required for the tests inserted via load.sql. In 5.4.20, they do not however. What is interesting is there are FK relations across the ISSUERS table rows to the parent RESOURCES table as it is a secondary JOIN table, but it is not being violated in 5.4.20. So, I would hypothesize that something perhaps in the MultiLine extractor has changed? I did notice there was a backport of a change in that area in 5.4.20 in the issues list. But the problem appears to be on the “creation” side and not a regression in the actual query itself. Which explains why the exact query works in 5.4.19 but fails in 5.4.20 which was utterly confusing for a bit 🙂 I am going to see if I can convert to not using the multi line reader in persistence.xml and if that makes any difference. But the issue appears to be related to the creation/loading of the database via the persistence.xml and not the runtime query failing so to speak. ( https://hibernate.atlassian.net/browse/HHH-14152#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14152#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14153) HQL update query with multiple condition generates temporary tables on SQLServer

by François DAMBRINE (JIRA)

François DAMBRINE ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c07a50... ) *commented* on HHH-14153 ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiMWQwOD... ) Re: HQL update query with multiple condition generates temporary tables on SQLServer ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiMWQwOD... ) I uploaded the case, let me know if it is not what you expected. ( https://hibernate.atlassian.net/browse/HHH-14153#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14153#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14153) HQL update query with multiple condition generates temporary tables on SQLServer

by François DAMBRINE (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14153) HQL update query with multiple condition generates temporary tables on SQLServer

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14153 ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiMjUwYW... ) Re: HQL update query with multiple condition generates temporary tables on SQLServer ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiMjUwYW... ) Well, this issue is about the avoidance of the temporary table altogether and the old issue is about the collation. Thanks, a test with the template will really help us further analyzing this. ( https://hibernate.atlassian.net/browse/HHH-14153#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14153#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14153) HQL update query with multiple condition generates temporary tables on SQLServer

by François DAMBRINE (JIRA)

François DAMBRINE ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c07a50... ) *commented* on HHH-14153 ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiOGQ3OD... ) Re: HQL update query with multiple condition generates temporary tables on SQLServer ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiOGQ3OD... ) For me they are strongly related but not duplicated The ancient ticket just talks about the collation of temp table. Of my understanding it affects the queries we could run by ourselves that use temp tables. My ticket talks about a specific query that ends up having temp table created where it is not needed. While https://hibernate.atlassian.net/browse/HHH-3326 is open this ticket generates a blocking error and the query cannot be processed. But the temp table query is still overkill for such update query. At the beginning I thought it was because of the presence of UUID identifier but if I use only one condition in the query there are no temp table created. I found your test template, I will try to provide you a test case. ( https://hibernate.atlassian.net/browse/HHH-14153#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14153#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14153) HQL update query with multiple condition generates temporary tables on SQLServer

by Nathan Xu (JIRA)

Nathan Xu ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14153 ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiNjczMj... ) Re: HQL update query with multiple condition generates temporary tables on SQLServer ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiNjczMj... ) seems a duplicate of that ancient ticket. ( https://hibernate.atlassian.net/browse/HHH-14153#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14153#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#100144- sha1:b6d623e )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-14153) HQL update query with multiple condition generates temporary tables on SQLServer

by François DAMBRINE (JIRA)

François DAMBRINE ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5c07a50... ) *commented* on HHH-14153 ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiNDUzZj... ) Re: HQL update query with multiple condition generates temporary tables on SQLServer ( https://hibernate.atlassian.net/browse/HHH-14153?atlOrigin=eyJpIjoiNDUzZj... ) I don’t know how to extract a test case out of this. If you can provide some tips about it I will post one. Here is the minimal model to reproduce the issue @Entity(name = "abstracttaskentity" ) @Inheritance(strategy = InheritanceType.JOINED) public abstract class AbstractTaskEntity { @Id @Type(type = "uuid- char " ) @Column(name = "id" ) private UUID taskId; @NotNull private String name; private String description; private boolean locked; public UUID getTaskId() { return taskId; } public void setTaskId(UUID taskId) { this.taskId = taskId; } public boolean isLocked() { return locked; } /** * @param locked */ public void setLocked( boolean locked) { this.locked = locked; } public String getName() { return name; } /** * @param name */ public void setName( String name) { this.name = name; } public String getDescription() { return description; } /** * @param description */ public void setDescription( String description) { this.description = description; } } Then one implementing class @Entity(name = "webtaskentity" ) public class WebTaskEntity extends AbstractTaskEntity { private String sessionId; public String getSessionId() { return sessionId; } public void setSessionId( String sessionId) { this.sessionId = sessionId; } } To have more information : the entity is persisted through the entity manager by a web handler. Then a background-running thread find out the task and tries to lock it with the query I gave in the issue. ( https://hibernate.atlassian.net/browse/HHH-14153#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14153#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#100144- sha1:b6d623e )

4 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 2020