We have a specific scenario where queries have to be constructed using both KEY(xyz) function and JOIN abc ON [predicate].
Support for extended JOIN [...] ON [...] was added in 4.3.0 which is great. Unfortunately re-introducing HHH-6103 in a different form as indicated here, makes JPA querying useless in our case. So... we are forced to drop back to using native SQL.
This is a major defect and I am surprised it was not picked up by the functional testing when upgrading from 4.2.9 to 4.3.0. The effect of HHH-8885 has the same severity as HHH-6103 and can be seen as functional regression. Please address it as a matter of urgency.
Note: we've attempted using both JPA QL and Criteria API with the same results across 4.2.9 and 4.3.0+
|
