Christian Beikov

Results 516 comments of Christian Beikov

>However, when I manually crafted a multi-value insert query, the execution time drastically improved to just 0.5 seconds. What database is this? I would say that the JDBC driver implementation...

Looks like a concurrency issue, but I have to think through this a bit to understand how this can happen.

Note that this query doesn't make a lot of sense which is why I'll assign a low priority, but I agree that it should ideally be fixed to skip duplicates...

A reproducer that uses just the core `CriteriaBuilder` API would be very helpful.

Don't worry about this. I think I have a test for this, but did not find the time yet to fix this as it is rather complex.

I think you can workaround this by disabling implicit group by generation for the select clause: https://persistence.blazebit.com/documentation/1.6/core/manual/en_US/#IMPLICIT_GROUP_BY_FROM_SELECT

It might be that BP expands an entity alias in group by to all the properties in order to workaround some Hibernate translation issues.

Standard QueryDSL does not attempt to create an implicit group by clause, that's why it works. Blaze-Persistence tries to match the needs of SQL when Hibernate fails to do so....