JPA query hints should not be stored in java.util.HashMap #348
Currently hints are stored in java.util.HashMap instance. The problem is that this does not permit duplicate keys, which is required for some eclipselink hints, for example (using JPA TypedQuery):
If query returns list of persons (with lazy adresses), this hint will tell eclipselink to fetch addresses upon access using single aditional select (one for home, one for work address) with IN clause, preventing N+1 problem.
"eclipselink.join-fetch" and "eclipselink.left-join-fetch" hints would too suffer from the same problem.
The text was updated successfully, but these errors were encountered: