Support #11066
Updated by Greg Shah 7 months ago
Hi guys,
In OpenEdge it's possible to specify temp-table parameters as "by-reference".
See: https://docs.progress.com/bundle/openedge-develop-abl-applications/page/Pass-a-temp-table-by-reference.html
Using this option avoids copying of temp-tables when making calls to an internal procedure.
How does FWD handle temp-table parameters? In the same way as OpenEdge? Does it make sense to add "by-reference" in the ABL, to speed up FWD?
If so: is it a big difference? After how many records (ballpark estimate) is it worthwhile? I can imagine that a temp-table of 50-100 small records won't be impacted much.
Hope you guys can shed some light on this. I browsed the documentation/wiki-page but couldn't find much; so perhaps you guys can add the answer to the wiki as wel. Thanks in advance!
In OpenEdge it's possible to specify temp-table parameters as "by-reference".
See: https://docs.progress.com/bundle/openedge-develop-abl-applications/page/Pass-a-temp-table-by-reference.html
Using this option avoids copying of temp-tables when making calls to an internal procedure.
How does FWD handle temp-table parameters? In the same way as OpenEdge? Does it make sense to add "by-reference" in the ABL, to speed up FWD?
If so: is it a big difference? After how many records (ballpark estimate) is it worthwhile? I can imagine that a temp-table of 50-100 small records won't be impacted much.
Hope you guys can shed some light on this. I browsed the documentation/wiki-page but couldn't find much; so perhaps you guys can add the answer to the wiki as wel. Thanks in advance!