Kbase P22525: Does adding a database trigger affect the CRC of a table or field in the schema?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
GOAL:
Does adding a database trigger affect the CRC of a table or field in the schema?
GOAL:
Is another compile needed after adding a database trigger?
GOAL:
What happens when the "Check CRC" check-box is checked?
FIX:
If you already have your application running in production mode and decide later to add schema triggers (at the table or field level), you do not have to recompile your application code. Schema triggers are not used in calculating database CRCs. Therefore, adding the triggers will not cause the CRCs to change and your .r code will not be affected.
There are CRC values, however, that can be involved with schema triggers. When the triggers are first created, you have the choice of whether or not you want CRCs used to manage your trigger code. These CRCs are separate CRC values that are computed for the trigger routines themselves. The Data Dictionary calculates these r-code CRC values and stores them in the _File-Trig (for table triggers)
and _Field-Trig (for field triggers). When a database event occurs in your application that causes a schema trigger to fire, if CRC checking is enabled, the CRC value of the trigger code is compared to the CRC value stored in the metaschema file. If they do not match, Progress returns a run-time error.