July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16923) Deleting all entities of a given type fails when using a composite primary key

by Andrea Boriero (JIRA)

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16923) Deleting all entities of a given type fails when using a composite primary key

by Andrea Boriero (JIRA)

2 years, 9 months

1
0
0 / 0

[JIRA] (HV-1958) ValidatorImpl ignore nodeName passed from ValueExtractor and does not add to propertyPath of ConstraintViolationExceptions

by Çağatay Sel (JIRA)

Çağatay Sel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63e2e8f... ) *updated* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiNzUwOWY4OTViY... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1958?atlOrigin=eyJpIjoiNzUwOWY4... ) HV-1958 ( https://hibernate.atlassian.net/browse/HV-1958?atlOrigin=eyJpIjoiNzUwOWY4... ) ValidatorImpl ignore nodeName passed from ValueExtractor and does not add to propertyPath of ConstraintViolationExceptions ( https://hibernate.atlassian.net/browse/HV-1958?atlOrigin=eyJpIjoiNzUwOWY4... ) Change By: Çağatay Sel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63e2e8f... ) I’ve a custom ValueExtractor for a wrapper object that keeps data in “data” property as follows: {noformat}public class NeedHelpValueExtractor implements ValueExtractor<MyWrapperObject<@ExtractedValue ?>> { @Override public void extractValues(MyWrapperObject<?> myWrapperObject, ValueExtractor.ValueReceiver receiver) { receiver.value("data", myWrapperObject.getData()); } }{noformat} I’m passing the nodeName parameter as “data” which is the name of the attribute in MyWrapperObject that gets validated. I’m able to do the validation with the above configuration as long as there are not any constraint violation. When a constraint violation occurs I get this exception: {{JSR-303 validated property 'myTestAttribute' does not have a corresponding accessor for Spring data binding}} When i debugged the SpringValidatorAdapter.java, I’ve noticed that the ConstraintViolationException has the wrong path and it does not contain the nodeName “data” that I’ve passed in ValueExtractor. Correct patch should be “data.myTestAttribute” but since it is passed as “myTestAttribute” it can’t be accessed from the wrapper object. When I further debugged, I’ve noticed that ValidatorImply.java is not using the nodeName while building BeanValueContext which can be seen from the below image. This cascadedValueContext is being used to construct ConstraintViolationExceptions further down the method chain. !image-20230713-141212.png|width=1251,height=539! ( https://hibernate.atlassian.net/browse/HV-1958#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1958#add-comment?atlOrigin=eyJp... ) 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#100231- sha1:2991753 )

2 years, 9 months

1
0
0 / 0

[JIRA] (HV-1958) ValidatorImpl ignore nodeName passed from ValueExtractor and does not add to propertyPath of ConstraintViolationExceptions

by Çağatay Sel (JIRA)

Çağatay Sel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63e2e8f... ) *created* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiMTgwMmIwMjk1N... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1958?atlOrigin=eyJpIjoiMTgwMmIw... ) HV-1958 ( https://hibernate.atlassian.net/browse/HV-1958?atlOrigin=eyJpIjoiMTgwMmIw... ) ValidatorImpl ignore nodeName passed from ValueExtractor and does not add to propertyPath of ConstraintViolationExceptions ( https://hibernate.atlassian.net/browse/HV-1958?atlOrigin=eyJpIjoiMTgwMmIw... ) Issue Type: Bug Affects Versions: 8.0.0.Final Assignee: Unassigned Attachments: image-20230713-141212.png Components: validators Created: 13/Jul/2023 07:12 AM Environment: hibernate-validator-8.0.0-Final Labels: validation Priority: Major Reporter: Çağatay Sel ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63e2e8f... ) I’ve a custom ValueExtractor for a wrapper object that keeps data in “data” property as follows: public class NeedHelpValueExtractor implements ValueExtractor<MyWrapperObject<@ExtractedValue ?>> { @Override public void extractValues(MyWrapperObject<?> myWrapperObject, ValueExtractor.ValueReceiver receiver) { receiver.value("data", myWrapperObject.getData()); } } I’m passing the nodeName parameter as “data” which is the name of the attribute in MyWrapperObject that gets validated. I’m able to do the validation with the above configuration as long as there are not any constraint violation. When a constraint violation occurs I get this exception: JSR-303 validated property 'myTestAttribute' does not have a corresponding accessor for Spring data binding When i debugged the SpringValidatorAdapter.java, I’ve noticed that the ConstraintViolationException has the wrong path and it does not contain the nodeName “data” that I’ve passed in ValueExtractor. Correct patch should be “data.myTestAttribute” but since it is passed as “myTestAttribute” it can’t be accessed from the wrapper object. When I further debugged, I’ve noticed that ValidatorImply.java is not using the nodeName while building BeanValueContext which can be seen from the below image. ( https://hibernate.atlassian.net/rest/api/3/attachment/content/50500 ) ( https://hibernate.atlassian.net/browse/HV-1958#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1958#add-comment?atlOrigin=eyJp... ) 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#100231- sha1:2991753 )

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16934) Fetching multiple fields of the same base class with InheritanceType.SINGLE_TABLE throws PropertyAccessException

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16934 ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiYmNkMT... ) Re: Fetching multiple fields of the same base class with InheritanceType.SINGLE_TABLE throws PropertyAccessException ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiYmNkMT... ) Hello Jan Friedrich ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) , thanks for reporting the issue. From what you’ve described, this seems closely related to https://hibernate.atlassian.net/browse/HHH-16494 , in that you’re trying to (left) join an association to a sub-type entity in an inheritance structure, and expect only the records corresponding to that sub-type to be joined. To be sure of this, though, we would need to see the complete mapping of you model or, even better, you could provide a simplified reproducer using our test case templates ( https://github.com/hibernate/hibernate-test-case-templates ). Meanwhile, the issue I mentioned has a work in progress fix, you can follow that for any updates. ( https://hibernate.atlassian.net/browse/HHH-16934#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16934#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#100231- sha1:2991753 )

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16934) Fetching multiple fields of the same base class with InheritanceType.SINGLE_TABLE throws PropertyAccessException

by Jan Friedrich (JIRA)

Jan Friedrich ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjEyYTc2MDM0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiMjEyYT... ) HHH-16934 ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiMjEyYT... ) Fetching multiple fields of the same base class with InheritanceType.SINGLE_TABLE throws PropertyAccessException ( https://hibernate.atlassian.net/browse/HHH-16934?atlOrigin=eyJpIjoiMjEyYT... ) Issue Type: Bug Affects Versions: 6.2.5 Assignee: Unassigned Components: hibernate-core Created: 13/Jul/2023 06:55 AM Priority: Major Reporter: Jan Friedrich ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) We are using a single address table with InheritanceType.SINGLE_TABLE and a simple discriminator value: @Entity @Table(name = "CUSTOMER_ADDRESS") @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="address_type", discriminatorType = DiscriminatorType.STRING) public abstract class CustomerAddressEntity {...} @Entity @DiscriminatorValue("H") public class CustomerAddressLegalEntity extends CustomerAddressEntity {...} @Entity @DiscriminatorValue("V") public class CustomerAddressMailingEntity extends CustomerAddressEntity {...} We are using a query that selects a single case, the customer assigned to the case and the addresses of the customer: SELECT ca FROM CaseEntity ca LEFT JOIN FETCH ca.customer cu LEFT JOIN FETCH cu.customerAddressLegal cal LEFT JOIN FETCH cu.customerAddressMailing cam WHERE ca.caseId = :caseId When we used Spring Boot 2.x, the generated SQL contained joins like this: left outer join customer_address customerad14_ on customeren12_.customer_id=customerad14_.customer_id and customerad14_.address_type='V' After switching to Spring Boot 3.x / Hibernate 6.x, the SQL looks like this - the condition on the discriminator column is missing: from case c1_0 left join customer c2_0 on c2_0.customer_id=c1_0.customer_id left join customer_address c3_0 on c2_0.customer_id=c3_0.customer_id left join customer_address c4_0 on c2_0.customer_id=c4_0.customer_id where c1_0.case_id=? An exception is thrown: Caused by: org.hibernate.PropertyAccessException: Could not set value of type [my.package.CustomerAddressLegalEntity] : `my.package.CustomerEntity.customerAddressMailing` (setter) at org.hibernate.property.access.spi.SetterFieldImpl.set(SetterFieldImpl.java:86) at org.hibernate.persister.entity.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:4187) at org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.initializeEntityInstance(AbstractEntityInitializer.java:844) at org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.initializeEntity(AbstractEntityInitializer.java:804) at org.hibernate.sql.results.graph.entity.AbstractEntityInitializer.initializeInstance(AbstractEntityInitializer.java:790) at org.hibernate.sql.results.internal.InitializersList.initializeInstance(InitializersList.java:70) at org.hibernate.sql.results.internal.StandardRowReader.coordinateInitializers(StandardRowReader.java:111) at org.hibernate.sql.results.internal.StandardRowReader.readRow(StandardRowReader.java:87) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:199) at org.hibernate.sql.results.spi.ListResultsConsumer.consume(ListResultsConsumer.java:33) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:361) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:168) at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.list(JdbcSelectExecutorStandardImpl.java:93) at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:31) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.lambda$new$0(ConcreteSqmSelectQueryPlan.java:110) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.withCacheableSqmInterpretation(ConcreteSqmSelectQueryPlan.java:303) at org.hibernate.query.sqm.internal.ConcreteSqmSelectQueryPlan.performList(ConcreteSqmSelectQueryPlan.java:244) at org.hibernate.query.sqm.internal.QuerySqmImpl.doList(QuerySqmImpl.java:518) at org.hibernate.query.spi.AbstractSelectionQuery.list(AbstractSelectionQuery.java:367) at org.hibernate.query.spi.AbstractSelectionQuery.getSingleResult(AbstractSelectionQuery.java:473) ( https://hibernate.atlassian.net/browse/HHH-16934#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16934#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#100231- sha1:2991753 )

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16917) Number not allowed as type for procedure query parameter

by Steve Ebersole (JIRA)

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16849) When we use partition key in join columns generated query is incorrect and its failing.

by Marco Belladelli (JIRA)

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16907) Improve performance of flushing

by Steve Ebersole (JIRA)

2 years, 9 months

1
0
0 / 0

[JIRA] (HHH-16907) Improve performance of flushing

by Steve Ebersole (JIRA)

2 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2023