Thanks for your feedback.
As I currently use QueryDSL generated queries, it's not easy to switch
the way my queries are generated.
I post an issue with a github branch with some simple test-cases here:
https://hibernate.atlassian.net/browse/HHH-12290
Laurent Almeras
Le 07/02/2018 à 19:43,
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
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 ;
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
Hi,
After digging further, it seems to me that there is a bug with Hibernate
5.3.
I debug and step through the query handling, and the generated QueryDSL
query seems correct to me:
=
select queuedTaskHolder
from QueuedTaskHolder queuedTaskHolder
where