Kbase P70968: Dynamics. Reasons to kep other logic out of the schema trigg
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/03/2004 |
|
Status: Unverified
GOAL:
Dynamics. Reasons to kep other logic out of the schema triggers
FIX:
Consider these reasons for removing logic from the database schema.
1. Any logic may possibly fail, or where a user could enter an incorrect value, should be on the client where a message can be formatted and presented to the user.
2. Field validatins from the schema are compiled into UI objects. If these validations reference the database, they cannot b running on the client side where there is no database access.
3. Legacy triggers may have been written with UI (such as message statement/alert boxes) inside them. This will not work in a distributed environment where the triggers are being executed by an AppServer with no UI.
4. Coding on the client also keeps the code "visible" to application developers rather than hidden in the schema.