PRO-IV using Oracle does an implicit COMMIT at the end of every program which commits any database changes to disk.
Does anyone know how to turn this 'feature' off and/or how to create a better 'transaction' which would consist of multiple programs but would not commit until the last of the program series had completed successfully.
Thanks.
Shane
Click the link below to see the new game I'm developing!
Transaction Boundaries
Started by
Guest_Shane Moore_*
, Jul 29 1999 03:55 AM
1 reply to this topic
#2
Joseph Serra
-
- Members
-
- 93 posts
Advanced
- Gender:Male
- Location:Melbourne, Australia
Posted 30 July 1999 - 02:50 PM
Shane
There is a value variable &#@SUPP-COMM that you can use to control the commit points. Enable it to suppress the automatic commits and control them yourself. Disable it to allow ProIV to work normally.
'#X = COMMIT()', '#X = ROLLBACK()' allows you to control the commits yourself.
Watch your rollback section size though. Apparently it can get rather large.
Joseph
There is a value variable &#@SUPP-COMM that you can use to control the commit points. Enable it to suppress the automatic commits and control them yourself. Disable it to allow ProIV to work normally.
'#X = COMMIT()', '#X = ROLLBACK()' allows you to control the commits yourself.
Watch your rollback section size though. Apparently it can get rather large.
Joseph
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
