Community
Participate
Working Groups
ExpressionOperator.coalesce can be overwritten by a platform, but it has no effect, cause Expression.coalesce is used at the end and the latter can not be configured for other platforms. MaxDB requires another functionname for coalesce
Setting initial target and priority. Please feel free to change either of these values when you know what the target is.
Created attachment 180062 [details] Rought Suggestion for a fix I am attaching a patch that should allow coalesce to be overridable. I have done some minimal testing on it, but it it still needs full testing.
Created attachment 180207 [details] Rough patch adding a prototype for a patch. testing and review is still required.
Tested successfully on MaxDB, which requires overwriting "COALESCE" by "VALUES". As we are targeting the MaxDB platform for 2.2, we'd need this patch in 2.2 as well.
Fixed in trunk. The fix changes coalesce, case, and caseCondition to get their Operator by lookup instead of creating it each time it is called. The fix also makes some changes to the flow in ArgumentListExpressionOperator to allow it to be overridden. Tested manually. Automated testing coming with implementation of bug 284657. Reviewed by Chris Delahunt
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink