Kbase P67948: Why all transactions are not kept in the _Trans VST
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/13/2009 |
|
Status: Verified
GOAL:
Why all transactions are not kept in the _Trans VST
GOAL:
Why isn't a transaction showing in the _Trans VST?
GOAL:
Do read only transactions appear in the _Trans VST?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
FOR EACH CUSTOMER EXCLUSIVE:
DISPLAY PHONE.
MESSAGE TRANSACTION VIEW-AS ALERT-BOX.
END.
A transaction is there but nothing appears in the _TRANS table.
Is the _TRANS table only related to Database Changes?
Is there different "levels" of what we consider transactions?
Should we consider the Transaction concept as something separate from the _Trans table?
FIX:
Transaction starts are buffered in the database transaction manager, such that the transaction begin note is not generated until the transaction makes a change to the database.
If it never does, then when it ends, /both/ the transaction begin note and the transaction end note are discarded.
If you had multiple databases attached, and you only did an actual update to one, the others would not show a transaction either.
We do not start database transactions unless we have to.