Re: [hibernate-dev] Removing dom4j?

The woodstox dependency is incompatible with the rest of the XML API due to a bug in the JDK that is otherwise hidden in all cases in the default implementation. Specifically it's implementation of EndElement brings that bug to the forefront, when

Re: [hibernate-dev] Removing dom4j?

Hi Jordan, I think it would be great to remove it. Especially recently we've started exploring what it would take to convert all jars into proper Jigsaw modules, and a requirement is that all dependencies need to be converted as well; this is obviously more problematic for such old libraries so

Re: [hibernate-dev] API incompatibilities between Hibernate ORM 5.3 and 6.0

I talked with Andrea and we both think this is getting important to do. So Monday we will start the process of integrating master (5.3) on to 6.0. Then you'll be able to have a better idea. This figures to be a huge undertaking, so not sure when it will be done. On Thu, Feb 15, 2018 at 10:05 PM

Re: [hibernate-dev] Empty IN list support

Thanks for reminding the JIRA, I see there's quite some people interested in it. I've added a comment explaining our plans, I guess many are not aware of our bigger picture. On 16 February 2018 at 10:57, Bregler, Jonathan wrote: > Ok, thanks. For some reason I missed

Re: [hibernate-dev] Empty IN list support

Ok, thanks. For some reason I missed the Jira issue. - Jonathan From: Guillaume Smet [mailto:guillaume.s...@gmail.com] Sent: Friday, February 16, 2018 11:39 AM To: Vlad Mihalcea Cc: Bregler, Jonathan ; hibernate-dev@lists.jboss.org Subject: Re:

Re: [hibernate-dev] Empty IN list support

See this related issue: https://hibernate.atlassian.net/browse/HHH-8091 On Fri, Feb 16, 2018 at 11:23 AM, Vlad Mihalcea wrote: > I see that we are only using it for testing so that we can skip the: > > testEmptyInListQuery > > query on certain Dialects. > > We could use

Re: [hibernate-dev] Empty IN list support

I see that we are only using it for testing so that we can skip the: testEmptyInListQuery query on certain Dialects. We could use this info when rendering the JPQL/HQL queries to throw an exception before executing the query. Nevertheless, an exception will be thrown anyway even if we don't do