[hibernate-dev] Hibernate ORM 5.2.13.Final has been released

*For details:http://in.relation.to/2018/02/07/hibernate-orm-5213-final-release * ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hiber

[hibernate-dev] Hibernate Search 5.9.0.Final released

Hello, We just published 5.9.0.Final, the first stable release in the 5.9 branch. This release brings a brand-new JSR-352 integration for mass indexing, WildFly feature packs, and better integration to modular environments. Check out our blog for more information about this release: http://in.re

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

Ok, so this is the crux then because it really comes down to whether you believe whether it is valid to *only* export the annotation-based validations as DDL. And keep in mind that this code is basically unchanged from all the way back to the initial "integrations" with HV. So back then the thoug

Re: [hibernate-dev] Some insight about HHH-12101 / remove HQL-style positional parameters

Yes, I can see this being a problem. Its caused by some very old, fulgy code in how "list-valued parameters" are handled internally. I'm not sure the best way to deal with this. Unfortunately reverting this is not possible - its necessary for JPA compliance. The simple workaround of course is t

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

2018-02-07 16:08 GMT+01:00 Steve Ebersole : > Ok, so this is the crux then because it really comes down to whether you > believe whether it is valid to *only* export the annotation-based > validations as DDL. > > And keep in mind that this code is basically unchanged from all the way > back to the

[hibernate-dev] ORM documentation info hibernate.org

Now that the hibernate.org infrastructure supports doc versions, should we remove the version drop-down from the info pages? Vlad I know you spent some time adding that; what are your thoughts? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org

Re: [hibernate-dev] ORM documentation info hibernate.org

I think it is not necessary anymore, so +1 for removing it. On 7 February 2018 at 18:32, Steve Ebersole wrote: > Now that the hibernate.org infrastructure supports doc versions, should we > remove the version drop-down from the info pages? Vlad I know you spent > some time adding that; what are

Re: [hibernate-dev] Some insight about HHH-12101 / remove HQL-style positional parameters

Yes, I understood the situation. I'm saying that in your query you should just be able to switch to use named parameters (prefixed with `:`, rather than `?`) as a workaround On Wed, Feb 7, 2018 at 11:21 AM Laurent Almeras wrote: > Hi, > > Thanks for this insight ; but as I stated (and this is a

Re: [hibernate-dev] ORM documentation info hibernate.org

I also think it's redundant now. Vlad On Wed, Feb 7, 2018 at 8:36 PM, andrea boriero wrote: > I think it is not necessary anymore, so +1 for removing it. > > On 7 February 2018 at 18:32, Steve Ebersole wrote: > > > Now that the hibernate.org infrastructure supports doc versions, should > we >

Re: [hibernate-dev] Some insight about HHH-12101 / remove HQL-style positional parameters

And I did say that this is indeed a problem assuming you are right, and I have no reason to believe you are not. In fact I can see how that would happen. Yes all based on Hibernate internals. So I am not trying to blow you off as "this is not a bug". I think it is a bug. I'm just saying I do n

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

Of course you can. `mode = CALLBACK,DDL` You mean that you cannot using single-valued setting On Wed, Feb 7, 2018 at 12:02 PM Gunnar Morling wrote: > 2018-02-07 16:08 GMT+01:00 Steve Ebersole : > >> Ok, so this is the crux then because it really comes down to whether you >> believe whether it

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

Right, giving multiple values isn't allowed as per JPA's XSD. 2018-02-07 19:44 GMT+01:00 Steve Ebersole : > Of course you can. `mode = CALLBACK,DDL` > > You mean that you cannot using single-valued setting > > On Wed, Feb 7, 2018 at 12:02 PM Gunnar Morling > wrote: > >> 2018-02-07 16:08 GMT+01:

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

How is a String "CALLBACK,DDL" considered "multiple values" to an XSD? Look, I don't mind revisiting a change here. I really have no horse n this race - this is not even my code originally. TBH I thought this was code that you did. So I don't mind changes here if there is a consensus. But let'

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

> How is a String "CALLBACK,DDL" considered "multiple values" to an XSD? I was referring to the dedicated element, which is restricted to the values AUTO, CALLBACK, NONE in that XSD and which can be given at most once [1]. I can see though how it'd work with the javax.persistence.validation.mode

Re: [hibernate-dev] ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

No, I think you are right and `hibernate.validator.apply_to_ddl` should apply to CALLBACK as well. On Wed, Feb 7, 2018 at 1:45 PM Gunnar Morling wrote: > > How is a String "CALLBACK,DDL" considered "multiple values" to an XSD? > > I was referring to the dedicated element, which is > restricted

Re: [hibernate-dev] ORM documentation info hibernate.org

No strong objection, but I quite like it giving a quick shortcut to switch version. It's also well visible, making sure people are on the version they mean to be - which is useful if they "land" directly on a version documentation from outdated links or search engines. On 7 February 2018 at 18:

Re: [hibernate-dev] ORM documentation info hibernate.org

That's a good thought. On Wed, Feb 7, 2018, 3:52 PM Sanne Grinovero wrote: > No strong objection, but I quite like it giving a quick shortcut to > switch version. > > It's also well visible, making sure people are on the version they > mean to be - which is useful if they "land" directly on a ve