July 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HBX-2063) Investigate class 'org.hibernate.tool.ide.completion.HQLCodeAssist' to fix the failing tests in 'org.hibernate.tool.ide.completion.ModelCompletion.TestCase'

by Koen Aers (JIRA)

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14131) NativeSQLQueryConstructorReturn is not processed by SQLQueryReturnProcessor

by Adrian Riley (JIRA)

Adrian Riley ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f23cba... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDUyODdjZmRh... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14131?atlOrigin=eyJpIjoiZDUyOD... ) HHH-14131 ( https://hibernate.atlassian.net/browse/HHH-14131?atlOrigin=eyJpIjoiZDUyOD... ) NativeSQLQueryConstructorReturn is not processed by SQLQueryReturnProcessor ( https://hibernate.atlassian.net/browse/HHH-14131?atlOrigin=eyJpIjoiZDUyOD... ) Change By: Adrian Riley ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f23cba... ) I am trying to call a stored procedure with 2 OUT parameters. I have declared a NamedStoredProcedureQuery referencing a SqlResultSetMapping: \ { \ { @NamedStoredProcedureQuery(name = " set_case_handler set_handler ", procedureName = " API_CUSTOMER_AGREEMENT_PKG API_CUSTOMER_PKG. set_case_handler set_handler ", parameters = \ { @StoredProcedureParameter(mode = ParameterMode.IN, name = "p_agreement_id", type = String.class), @StoredProcedureParameter(mode = ParameterMode.OUT, name = "p_success_o", type = Integer.class), @StoredProcedureParameter(mode = ParameterMode.OUT, name = "p_error_message_o", type = String.class) }, resultSetMappings = "procedure_result_mapping") @SqlResultSetMapping(name = "procedure_result_mapping", classes = \ { @ConstructorResult(targetClass = ProcedureResult.class, columns = \ { @ColumnResult(name = "p_success_o", type = Integer.class), @ColumnResult(name = "p_error_message_o", type = String.class) }) } }} The stored procedure is executed and produces a Map of the two output parameters. Then {{SQLQueryReturnProcessor.processReturn}} is called, which calls {{processConstructorReturn}}. But this method is empty, so the SqlResultSetMapping has no effect, and the Map is returned as the query result. Is this by design, or is the functionality just missing? ( https://hibernate.atlassian.net/browse/HHH-14131#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14131#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HBX-2062) Investigate failing setup of org.hibernate.tool.hbm2x.hbm2hbmxml.TypeParamsTest.Order.TestCase

by Koen Aers (JIRA)

Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Tools ( https://hibernate.atlassian.net/browse/HBX?atlOrigin=eyJpIjoiNjUyNGMzZjZj... ) / Task ( https://hibernate.atlassian.net/browse/HBX-2062?atlOrigin=eyJpIjoiNjUyNGM... ) HBX-2062 ( https://hibernate.atlassian.net/browse/HBX-2062?atlOrigin=eyJpIjoiNjUyNGM... ) Investigate failing setup of org.hibernate.tool.hbm2x.hbm2hbmxml.TypeParamsTest.Order.TestCase ( https://hibernate.atlassian.net/browse/HBX-2062?atlOrigin=eyJpIjoiNjUyNGM... ) Issue Type: Task Assignee: Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 31/Jul/2020 01:23 AM Fix Versions: 6.0.0.Alpha2 Priority: Major Reporter: Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Building the metadata from the hbm.xml file results in a null pointer: <hibernate-mapping> <class name= "org.hibernate.tool.hbm2x.hbm2hbmxml.TypeParamsTest.Order" table= "ORDERS" > <id name= "orderId" type= "long" > <column name= "ORDERID" /> <generator class= "native" /> </id> <property generated= "never" lazy= "false" name= "status" > <column name= "STATUS" /> <type name= "org.hibernate.type.EnumType" > <param name= "catalog" /> <param name= "column" > STATUS </param> <param name= "table" > ORDERS </param> <param name= "schema" /> <param name= "enumClass" > org.hibernate.tool.hbm2x.hbm2hbmxml.Order$Status </param> </type> </property> <property name= "name" type= "string" /> </class> </hibernate-mapping> ( https://hibernate.atlassian.net/browse/HBX-2062#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HBX-2062#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14131) NativeSQLQueryConstructorReturn is not processed by SQLQueryReturnProcessor

by Adrian Riley (JIRA)

Adrian Riley ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f23cba... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTE0ZGUwZGFk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14131?atlOrigin=eyJpIjoiOTE0ZG... ) HHH-14131 ( https://hibernate.atlassian.net/browse/HHH-14131?atlOrigin=eyJpIjoiOTE0ZG... ) NativeSQLQueryConstructorReturn is not processed by SQLQueryReturnProcessor ( https://hibernate.atlassian.net/browse/HHH-14131?atlOrigin=eyJpIjoiOTE0ZG... ) Issue Type: Bug Affects Versions: 5.4.19 Assignee: Unassigned Components: hibernate-core Created: 31/Jul/2020 00:55 AM Environment: hibernate-core-5.4.12.Final JDK8 Windows 10 & Linux Oracle Priority: Major Reporter: Adrian Riley ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f23cba... ) I am trying to call a stored procedure with 2 OUT parameters. I have declared a NamedStoredProcedureQuery referencing a SqlResultSetMapping: {{ @NamedStoredProcedureQuery(name = "set_case_handler", procedureName = "API_CUSTOMER_AGREEMENT_PKG.set_case_handler", parameters = { @StoredProcedureParameter(mode = ParameterMode.IN, name = "p_agreement_id", type = String.class), @StoredProcedureParameter(mode = ParameterMode.OUT, name = "p_success_o", type = Integer.class), @StoredProcedureParameter(mode = ParameterMode.OUT, name = "p_error_message_o", type = String.class) } , resultSetMappings = "procedure_result_mapping") @SqlResultSetMapping(name = "procedure_result_mapping", classes = { @ConstructorResult(targetClass = ProcedureResult.class, columns = { @ColumnResult(name = "p_success_o", type = Integer.class), @ColumnResult(name = "p_error_message_o", type = String.class) } ) } }} The stored procedure is executed and produces a Map of the two output parameters. Then SQLQueryReturnProcessor.processReturn is called, which calls processConstructorReturn. But this method is empty, so the SqlResultSetMapping has no effect, and the Map is returned as the query result. Is this by design, or is the functionality just missing? ( https://hibernate.atlassian.net/browse/HHH-14131#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14131#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14130) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries

by Erik Lumme (JIRA)

Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMzQyNzEwZjAy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiMzQyNz... ) HHH-14130 ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiMzQyNz... ) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiMzQyNz... ) Change By: Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider an entity with an ID of type Long. An entity can be found based on it's ID in a criteria query using a construct such as this {noformat}Root<TestEntity> root = cq.from(TestEntity.class); cq.where(root.in(1, 2, 3));{noformat} However, when setting {{hibernate.criteria.literal_handling_mode}} to {{BIND}}, this no longer works, but results in the error: {{java.lang.IllegalArgumentException: Parameter value [1] did not match expected type [org.hibernate.bugs.TestEntity (n/a)]}} Test case can be found on [GitHub|https://github.com/eriklumme/hibernate-bind-test/blob/master/src/t...]. The test case {{ hhhTest_works hhh14130_test_works }} passes, and {{ hhhTest_fails hhh14130_test_fails }} fails. ( https://hibernate.atlassian.net/browse/HHH-14130#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14130#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14130) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries

by Erik Lumme (JIRA)

Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDIwMjJhNjg5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiZDIwMj... ) HHH-14130 ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiZDIwMj... ) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiZDIwMj... ) Change By: Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider an entity with an ID of type Long. An entity can be found based on it's ID in a criteria query using a construct such as this {noformat} Root<TestEntity> root = cq.from(TestEntity.class); cq.where(root.in(1, 2, 3)); {noformat} However, when setting {{hibernate.criteria.literal_handling_mode}} to {{BIND}}, this no longer works, but results in the error: {{java.lang.IllegalArgumentException: Parameter value [1] did not match expected type [org.hibernate.bugs.TestEntity (n/a)]}} Test case can be found on [GitHub|https://github.com/eriklumme/hibernate-bind-test/blob/master/src/t...]. The test case {{hhhTest_works}} passes, and {{hhhTest_fails}} fails. ( https://hibernate.atlassian.net/browse/HHH-14130#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14130#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14130) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries

by Erik Lumme (JIRA)

Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTFlZTgxY2Rj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiNTFlZT... ) HHH-14130 ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiNTFlZT... ) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiNTFlZT... ) Change By: Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider an entity with an ID of type Long. An entity can be found based on it's ID in a criteria query using a construct such as this {{ Root<TestEntity> root = cq.from(TestEntity.class); cq.where(root.in(1, 2, 3)); }} However, when setting {{hibernate.criteria.literal_handling_mode}} to {{BIND}}, this no longer works, but results in the error: {{java.lang.IllegalArgumentException: Parameter value [1] did not match expected type [org.hibernate.bugs.TestEntity (n/a)]}} Test case can be found on [GitHub|https://github.com/eriklumme/hibernate-bind-test/blob/master/src/t...]. The test case {{hhhTest_works}} passes, and {{hhhTest_fails}} fails. ( https://hibernate.atlassian.net/browse/HHH-14130#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14130#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14130) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries

by Erik Lumme (JIRA)

Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiY2Y1Y2I2MzZl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiY2Y1Y2... ) HHH-14130 ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiY2Y1Y2... ) When setting "hibernate.criteria.literal_handling_mode" to "BIND", entities can't be compared to IDs in criteria queries ( https://hibernate.atlassian.net/browse/HHH-14130?atlOrigin=eyJpIjoiY2Y1Y2... ) Issue Type: Bug Affects Versions: 5.4.18 Assignee: Unassigned Components: hibernate-core Created: 31/Jul/2020 00:25 AM Priority: Minor Reporter: Erik Lumme ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Consider an entity with an ID of type Long. An entity can be found based on it's ID in a criteria query using a construct such as this {{Root<TestEntity> root = cq.from(TestEntity.class); cq.where(root.in(1, 2, 3));}} However, when setting hibernate.criteria.literal_handling_mode to BIND , this no longer works, but results in the error: java.lang.IllegalArgumentException: Parameter value [1] did not match expected type [org.hibernate.bugs.TestEntity (n/a)] Test case can be found on GitHub ( https://github.com/eriklumme/hibernate-bind-test/blob/master/src/test/jav... ). The test case hhhTest_works passes, and hhhTest_fails fails. ( https://hibernate.atlassian.net/browse/HHH-14130#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14130#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#100140- sha1:33445dc )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-13694) Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database

by William Watson (JIRA)

William Watson ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f23a24... ) *commented* on HHH-13694 ( https://hibernate.atlassian.net/browse/HHH-13694?atlOrigin=eyJpIjoiOTY4Y2... ) Re: Numeric Overflow Exception when retrieving the Meta-data for sequences from Oracle Database ( https://hibernate.atlassian.net/browse/HHH-13694?atlOrigin=eyJpIjoiOTY4Y2... ) There is a workaround for this bug here: https://stackoverflow.com/questions/58570032/hibernate-could-not-fetch-th... ( https://hibernate.atlassian.net/browse/HHH-13694#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13694#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#100140- sha1:8c1da53 )

3 years, 9 months

1
0
0 / 0

[JIRA] (HHH-14128) NullPointerException when building sessionFactory

by Nathan Xu (JIRA)

Nathan Xu ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14128 ( https://hibernate.atlassian.net/browse/HHH-14128?atlOrigin=eyJpIjoiYzQzZT... ) Re: NullPointerException when building sessionFactory ( https://hibernate.atlassian.net/browse/HHH-14128?atlOrigin=eyJpIjoiYzQzZT... ) You can set a breakpoint at AbstractLoadPlanBuildingAssociationVisitationStrategy Line #669 to narrow down the entity and the field. Maybe the one-to-many collection involve some class which is not specified as entity. Definitively a coding imperfection for the javadoc of {{org.hibernate.loader.plan.spi.FetchSource#resolveEntityReference()}}has said null value could be returned. Your persistence.xml seems not very helpful to narrow down the root cause, though, at least for someone who is not using JBoss product. ( https://hibernate.atlassian.net/browse/HHH-14128#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14128#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#100140- sha1:5beb332 )

3 years, 9 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 July 2020