Kbase P108553: 4GL/ABL: Does Progress search the PROPATH when the -trig client startup parameter is used?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/12/2008 |
|
Status: Verified
GOAL:
4GL/ABL: Does Progress search the PROPATH when the -trig client startup parameter is used?
GOAL:
What is the rationale behind having a specified directory or library independent of the PROPATH?
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
1. No, Progress does NOT search the PROPATH for the trigger code when the -trig client startup parameter is specified. It will only search the specified directory or library for the 4GL triggers.
2. One of the main reasons the -trig parameter was added is to prevent the database schema triggers from being found in the PROPATH. That enhances the trigger security by preventing applications and operating system commands from erroneously running, or accidentally deleting, modifying or overwriting the schema triggers as is likely to happen when an application procedure have the same name as a database schema trigger.
Additionally, it is just better organization and compartmentalization to have the triggers isolated in a directory or in a procedure library so that their maintenance does not occur accidentally thus maintaining their integrity and enforcing and enhancing their security.