Bug #4535
CONNECT statement with VALUE expression quirks
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
02/11/2020
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
Related issues
History
#1 Updated by Igor Skornyakov over 4 years ago
The VALUE usage in the CONNECT statement looks really tricky. For example
CONNECT VALUE("E:\testcases\uast\security\fwd1.db") -P secret -U fwdb@domain -bibufs 12 -1 -ld fwd1.
works fine in the 4GL.
However
CONNECT VALUE("E:\testcases\uast\security\fwd1.db -P secret") -U fwdb@domain -bibufs 13 -1 -ld fwd1.
fails in the 4GL with Warning: -ld is not a database parameter and was ignored. (1402).
Currently, FWD processes both statements identically.
See also #3813-40
#2 Updated by Igor Skornyakov over 4 years ago
- Related to Feature #3813: misc DB features part deux added