While the warning hints at the fact that this is like a keyed join, and the documentation for DENORMALIZE says that it is 'basically a specialized form of JOIN', it would be clearer if it made mention that the JOIN options also applied to DENORMALIZE (as appropriate).
Conclusion
None
Activity
Show:
Gavin Halliday March 22, 2016 at 9:52 AM
I think all options on JOIN also apply to DENORMALIZE. Most of the processing code tends to be identical, with only the last part different depending on the operation.
Kevin Logemann March 2, 2016 at 6:48 PM
It seems odd that LOCAL and NOSORT are called out in the documentation, but none of the other JOIN options.
I wouldn't mind a one-liner in the documentation that references the options present in the JOIN documentation.
However, are any of the options only applicable to JOIN and not DENORMALIZE?
Jim DeFabia March 2, 2016 at 4:10 PM
Thanks
Your thoughts?
Richard Taylor March 2, 2016 at 4:03 PM
We deliberately did not document all available options on DENORMALIZE. The fact is that DENORMALIZE is really just a special-case JOIN, so adding all the options JOIN has (that would be used on DENORMALIZE extremely infrequently) was deemed unnecessary after discussion with GH & RKC, a long time ago.
If it is now deemed to be necessary, then I would suggest a one-liner in the DENORMALIZE docs stating just what I said above and pointing to the JOIN docs.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
In the effort to remove all ECL warnings from production code, developers encountered the following warning from a Keyed DENORMALIZE:
Warning: klogemann.TestDenormService (Line 28, Column 20: Code 4522) Implicit LIMIT(10000) added to keyed join '~foreign::10.194.12.1::THOR::KEY::CD::HOLDER_QA'
While the warning hints at the fact that this is like a keyed join, and the documentation for DENORMALIZE says that it is 'basically a specialized form of JOIN', it would be clearer if it made mention that the JOIN options also applied to DENORMALIZE (as appropriate).