Hi,
HANA doesn't support empty IN lists, so executing an HQL query that gets
transformed into a SQL query with an empty IN list results in a SQL parser
error on the database side. I noticed that the Dialect class already defines a
method called "supportsEmptyInList()" which according to the Jav
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 i
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 this info when rendering
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: [hibernate-dev] Empty IN list support
See this rel
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 the Jira issue.
>
> - Jonath
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
So, the library has not seen a bugfix in over 10 years, and it lists the
wrong version for it's xml-apis dependency.
There are some notes in comments about eventually removing it, and I
thought I'd give it a try on the 5.2 branch.
I had to remove two shiv-libraries you had added to work around prob
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 it
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
com.sun.org.apache.xalan.internal.xsltc.trax.StAXE