Re: [hibernate-dev] 5.1 tentative release date

I'll create a jira for the Javassist to be part of 5.1. Should we also look at changing Hibernate to not require Javassist classes be on the deployment classpath? This might require cloning some Javassist runtime classes so that we don't get CNFE on javassist.util.proxy.ProxyObject (and whatev

Re: [hibernate-dev] 5.1 tentative release date

I don't see a Jira to upgrade Javassist as part of 5.1... On Fri, Jan 8, 2016 at 1:35 PM Scott Marlow wrote: > Should we upgrade to javassist latest in 5.1 still? > > On 01/08/2016 10:08 AM, Steve Ebersole wrote: > > Just a heads up that I tentatively set Jan 27th as the release date for > > 5.

Re: [hibernate-dev] 5.1 tentative release date

Should we upgrade to javassist latest in 5.1 still? On 01/08/2016 10:08 AM, Steve Ebersole wrote: > Just a heads up that I tentatively set Jan 27th as the release date for > 5.1. Please let me know if that does not work for anyone. Also please > keep that date in mind if there is anything you wa

[hibernate-dev] HHH-9491 - Global quoting and "column definitions"

HHH-9491[1] is a report that discusses problems when requesting global quoting (what JPA calls delimited identifiers). My last comment[2] discusses 2 options for handling this. I'd like to get others thoughts. [1] https://hibernate.atlassian.net/browse/HHH-9491 [2] https://hibernate.atlassian.ne

Re: [hibernate-dev] Is the the optional=false @OneToOne lazy retrieval still relevant

Depending on exactly how you are testing that, that sounds like a bug. Are you (inadvertently) using bytecode enhancement? On Fri, Jan 8, 2016 at 9:09 AM Vlad Mihalcea wrote: > Hi, > > I remember that for a bidirectional @OneToOne relationship, the optional = > false attribute could instruct H

[hibernate-dev] 5.1 tentative release date

Just a heads up that I tentatively set Jan 27th as the release date for 5.1. Please let me know if that does not work for anyone. Also please keep that date in mind if there is anything you want to get into 5.1. ___ hibernate-dev mailing list hibernate-

[hibernate-dev] Is the the optional=false @OneToOne lazy retrieval still relevant

Hi, I remember that for a bidirectional @OneToOne relationship, the optional = false attribute could instruct Hibernate to always generate a Proxy (because this association cannot be null), so, if the fetch is LAZY, it would not generate a secondary query upon fetching the parent-side entity. I t

Re: [hibernate-dev] Not letting Jenkins auto-close PRs upon build failures

2016-01-08 14:39 GMT+01:00 Sanne Grinovero : > Do you have an example of such a PR being closed? Yes, https://github.com/hibernate/hibernate-ogm/pull/610 whose auto-closing half a dozen times nearly drove me nuts ;) > > For sure that was never our intention, but be aware that such options > can b

Re: [hibernate-dev] Not letting Jenkins auto-close PRs upon build failures

Do you have an example of such a PR being closed? For sure that was never our intention, but be aware that such options can be set globally on the ci server as project detaults, but can be overriden in a specific build task. So I'd check the build task which did this as for example Search PRs seem

Re: [hibernate-dev] should immutable entities in the second level cache be invalidated when they are removed from the database?

Since one can delete an immutable entity, and then create (insert) a new one to replace it, from the point of view of the Cache the entry is not immutable and needs to be treated with the usual safety and consistency concerns. As Radim suggests, optimizations like using a local cache might make se

Re: [hibernate-dev] The stable docs are outdated

Hi, On Thu, Jan 07, 2016 at 02:17:29PM +, Steve Ebersole wrote: > Second, is that really the intent for "stable"? When we first starting > doing "stable" the intent was to have stable URLs for bookmarking etc. > What you describe, and how we actually handle it (at least on the ORM > side), i