May 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16651) new ways to enable subselect fetching

by Gavin King (JIRA)

Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16651 ( https://hibernate.atlassian.net/browse/HHH-16651?atlOrigin=eyJpIjoiYTZhYj... ) Re: new ways to enable subselect fetching ( https://hibernate.atlassian.net/browse/HHH-16651?atlOrigin=eyJpIjoiYTZhYj... ) It’s still not finished though And we still need to properly discuss and review the work which has been done. ( https://hibernate.atlassian.net/browse/HHH-16651#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16651#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#100225- sha1:bbd69a1 )

1 year, 4 months

1
0
0 / 0

[JIRA] (HV-1949) Nondeterministic behavior of HibernateValidator (in springboot?) when both annotation and xml-based definition are used

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HV-1949 ( https://hibernate.atlassian.net/browse/HV-1949?atlOrigin=eyJpIjoiNjg2NDlk... ) Re: Nondeterministic behavior of HibernateValidator (in springboot?) when both annotation and xml-based definition are used ( https://hibernate.atlassian.net/browse/HV-1949?atlOrigin=eyJpIjoiNjg2NDlk... ) Alternatively, a more stable solution could be to use programmatic mapping API for everything and remove the XML + ServiceLoader: final HibernateValidatorConfiguration configuration = Validation.byProvider( HibernateValidator.class ).configure(); ConstraintMapping constraintMapping = configuration.createConstraintMapping(); configuration.addMapping( constraintMapping ); constraintMapping.constraintDefinition( AnyUuid.class ) .includeExistingValidators( true ) .validatedBy( AnyUuid.AnyUuidValidator.class ); constraintMapping.type( mwe.validatorfail.dto.SampleDTO.class ) // instead of an XML .getter( "uuid" ) .constraint( new AnyUuidDef() ) .constraint( new NotNullDef() ); ( https://hibernate.atlassian.net/browse/HV-1949#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1949#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#100225- sha1:bbd69a1 )

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16656) H2 1.4.200 lacks registration of ranking window functions

by Christian Beikov (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16656) H2 1.4.200 lacks registration of ranking window functions

by Christian Beikov (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16657) Type filter in subquery wrongly propagates as filter to table group

by Christian Beikov (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16657) Type filter in subquery wrongly propagates as filter to table group

by Christian Beikov (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16655) Parser error for window frames due to wrong rule order

by Christian Beikov (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16655) Parser error for window frames due to wrong rule order

by Christian Beikov (JIRA)

1 year, 4 months

1
0
0 / 0

[JIRA] (HV-1949) Nondeterministic behavior of HibernateValidator (in springboot?) when both annotation and xml-based definition are used

by Marko Bekhta (JIRA)

Marko Bekhta ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HV-1949 ( https://hibernate.atlassian.net/browse/HV-1949?atlOrigin=eyJpIjoiNDI2OWZi... ) Re: Nondeterministic behavior of HibernateValidator (in springboot?) when both annotation and xml-based definition are used ( https://hibernate.atlassian.net/browse/HV-1949?atlOrigin=eyJpIjoiNDI2OWZi... ) Hey martin mucha ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) , Thanks for providing a reproducer. I can confirm that the problem comes from the HV. What’s happening in this case right now is: HV has multiple sources from where it is reading the metadata: annotations, XML, API(programmatic and various ServiceLoaders). Each next source would have higher priority and can be used to override the previous configuration. Now what’s happening in your case: * HV reads XML, which has a reference to your custom constraint, but as that constraint doesn’t have a provided validator either as part of the definition or in the XML – the XML metadata provider “thinks” that there are no validators to be applied to this constraint. * HV “reads” programmatic definitions/ServiceLoadrs – finds a validator for your custom constraint and registers it. At this point, the constraint metadata from XML is not refreshed, and it still assumes that there are no validators. * When you execute the validation for the first time, depending on which route it goes, it will cache the ConstraintValidator for the validated type… If it is going the XML route first – no validators, and you get the exceptions…. If it is an annotation route – annotation metadata in Spring would get built lazily, and as a result, at that point, it would already know about the validator and cache it. Future XML/annotation-based calls will be using the cached instance, and no errors will appear. Until this is fixed, I can suggest that you add some quick validation call that will take an annotation route as part of the initialization process. Maybe if you have a configuration for the validator – add some post-construct action that would request a validator and make a validation call. Note this would only work if the constraint has the same definition (same annotation attributes) and the validated type is also the same + no changes to HibernateConstraintValidatorInitializationContext ( https://hibernate.atlassian.net/browse/HV-1949#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1949#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#100225- sha1:bbd69a1 )

1 year, 4 months

1
0
0 / 0

[JIRA] (HHH-16659) add SelectionQuery.setEntityGraph()

by Christian Beikov (JIRA)

1 year, 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 May 2023