Bug #3364
problems with TABLE-HANDLE and TABLE parameters related to BY-REFERENCE
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
Related issues
History
#1 Updated by Greg Shah over 6 years ago
- Related to Feature #3296: misc db features added
#2 Updated by Greg Shah over 6 years ago
This was initially reported in #3296-9.
The following TABLE-HANDLE and TABLE parameter problems exist:
- runtime for
TABLE-HANDLE ... BY-REFERENCE
- I don't have testcases yet, but code inTemporaryBuffer.createDynamicTable
should be similar toTemporaryBuffer.associate
- conversion for
BY-REFERENCE
andAPPEND
forTABLE-HANDLE
andTABLE
arguments at function calls: this is a parser issue too, asBY-REFERENCE
andAPPEND
are emitted as a sibling to i.e.TABLE-HANDLE
(as a direct child for the function call AST, i.e.FUNC_CHAR
), and the conversion rules assume thatBY-REFERENCE
orAPPEND
are arguments for the function call, and not options. Seeuast/temp_table_by_ref_c.p
which covers all the function/procedure cases forTABLE-HANDLE
andTABLE
, withBY-REFERENCE
and/orAPPEND
. Just uncomment the commented code to see the error.
Other tests are these:
added uast/temp_table_by_ref.p added uast/temp_table_by_ref2.p added uast/temp_table_by_ref3.p added uast/temp_table_by_ref_b.p added uast/temp_table_by_ref_c.p
#3 Updated by Eric Faulhaber over 5 years ago
- Related to Feature #3816: table and table handle parameter options added