After migrating to H3, several queries seem to be demonstrating odd behavior we didn't expect.

We had some Criteria queries that we'd previously have to distinct via a HashSet, which was expected. However, now it seems we need to do the same for the child Bags of same said entities. Whereas in H2.X we did not have to do this.

We can live with this, however, is this expected behavior in H3 given the Criteria makeover?

maybe you have multiple fetch joins - that was ignored in h2, but allowed with H3 but does not work with bags because it is not possible to distinguish between redundant entities.

Bang! Right on, Max. Thanks.

In this case, is it recommended to refactor the queries or simply distinct the bags?

I mean, is there any benefit to doing the former if the query works?

Cheers,
Roll

i would refactor the queries .... distincting the bags might remove duplicates that should be there.

Just for future readers, Max when you said:


You were referring to multiple fetch joins on collections as multiple fetch joining on associations was already allowed, I presume.

Moreover, I think that for our model distincting the bag is acceptable. However, it makes one wonder why we're not using a Set here. Thank you for your insight.