Feature #3295
improve connect options support per #3257-29
Start date:
Due date:
% Done:
100%
billable:
No
vendor_id:
GCD
version_reported:
version_resolved:
History
#1 Updated by Eric Faulhaber almost 7 years ago
Testing the CONNECT statement indicates the following rules in the 4GL:
- If you specify a physical database, it must come first after the CONNECT keyword.
- You do not need to include the
.db
extension in the PDB. - If you specify
-pf <parameter file>
, you can omit a PDB name- In this case, the PF file should contain a
-db
option. If not, the CONNECT silently fails. - So far,
-pf
is the only option I've found that is accepted if the PDB name is missing. Others produce an error. - You can specify other options in the CONNECT statement, along with the
-pf
option. They may come before or after the-pf
option.
- In this case, the PF file should contain a
- You can specify a PDB name in the CONNECT statement AND a PF file.
- If a PDB name exists in the PF file (i.e., with the
-db
option), the PDB name specified in the CONNECT statement is honored, and the one in the PF file is ignored.
- If a PDB name exists in the PF file (i.e., with the
- A PDB name cannot start with a hyphen; it appears the 4GL parser expects hyphen to begin an option name.
- If two
-pf
options are specified, only the last one appears to be honored. - The name of a database connect option is one of a few areas in Progress where case matters; the option names are case sensitive and options provided in the wrong case are ignored.
#2 Updated by Eric Faulhaber almost 7 years ago
- Status changed from New to WIP
Added conversion support for -1
, -pf
, and -RO
options in task branch 1514a/11397. Runtime support not yet added.
#3 Updated by Greg Shah over 6 years ago
- % Done changed from 0 to 100
- Status changed from WIP to Closed
-1
(single user mode) is processed on input and reported for DB-PARAM but is otherwise ignored. The customer reported that full runtime support is not needed.
-pf
is handled at conversion but not honored at runtime. The customer reported that runtime support is not needed.
-RO
is no longer in the latest code drop for the customer.
-ct
(connection retries) conversion and runtime support was added in 3296a which was merged to trunk as revision 11191.