[hibernate-dev] HHH-8999/HHH-10413 and Comparable IDs

ExecutableList#add attempts to keep track of whether the Executable objects are sorted. [1] Except for entity insert actions (which use InsertActionSorter), ExecutableList#add uses the following to determine if adding the current Executable to the end invalidates the sort: if ( previousLast !=

[hibernate-dev] JDBC uses ON_CLOSE connection release mode

I think this PR is valid: https://github.com/hibernate/hibernate-orm/pull/997 I checked it out and, when using JDBC, we use the ON_CLOSE connection release mode. Shouldn't we use the AFTER_TRANSACTION release mode as we state in the docs? Vlad ___

Re: [hibernate-dev] [Search] Travis support

I just learned that Travis makes it easy to compile with one JDK and then do something else with a different JDK - like running tests. That's very nice. With Jenkins we have to workaround such things by creating multiple jobs and linking them together as dependencies. On 2 February 2016 at

Re: [hibernate-dev] http://www.hibernatespatial.org/

Hi Vlad, Thanks for doing this already. It’s a good starting point. I’ll suggest a number of changes using a PR on the asciidoc and unit test sources in the coming weeks. Regards, Karel > On 25 Feb 2016, at 10:52, Vlad Mihalcea wrote: > > Hi Karel, > > I pushed

[hibernate-dev] Fwd: Build failed in Jenkins: hibernate-orm-master-h2-infinispan8.2 #83

Anyone plan on looking at these frequent transient failures anytime soon? If not, I plan on disabling this from running automatically. It's just white noise at this point. -- Forwarded message - From: Hibernate CI Date: Wed, Mar 2, 2016 at 8:22 AM Subject:

Re: [hibernate-dev] Java 1.8-specific code in hibernate-infinispan

Hi Vlad, thanks for bringing that up: I mean to start a thread here among the lines of my answers on twitter. The problem I see in our little survey is that in the way it was phrased it's not providing useful data for the purpose of understanding what we should be supporting in the next version

Re: [hibernate-dev] Java 1.8-specific code in hibernate-infinispan

Although Java 1.8 has seen a great adoption rate, on the enterprise side things always move very slowly. https://twitter.com/Hibernate/status/700998618824753152 Anyway, we shouldn't be stuck with 1.6 just because some legacy systems might not never migrate to a newer version. Other frameworks

Re: [hibernate-dev] Java 1.8-specific code in hibernate-infinispan

Btw., when does ORM plan to drop pre-8 support altogether? 6.0? Radim On 03/01/2016 10:18 PM, Steve Ebersole wrote: > Correct. hibernate-infinispan can use Java 8. As Sanne says, Infinispan > itself requires Java 8 so limiting hibernate-infinispan to > 8 really makes > no sense, > > On Tue,