Subject | Re: [IBO] concurrency locking and IBO-defaults |
---|---|
Author | L.M. Bemmelmans |
Post date | 2003-07-21T16:20:36Z |
Helen,
It's part an IBO question and part FB, so I decided to stay in the IBO
newsgroup for now.
I played along with tiConcurrency and perhaps I'm getting the point now.
Correct me if I'm wrong
1.JUST BEFORE a new select statement is the right place to do a hard COMMIT
(tiConcurrency)
2.after executing a select you can leave the transaction open for a while.
The timer will shut it down with a hard commit if there is no activity
3.commit retaining during posting is allright because other users will see
the changes you made immediately
(if the other users COMMIT before SELECT)
4.if you try to update a record already changed by an other user you will
get an error message
This means....
using tiConcurrency seems to be a way to be sure your record is the most
recent version. If not you'll get an error message.
Leon
It's part an IBO question and part FB, so I decided to stay in the IBO
newsgroup for now.
I played along with tiConcurrency and perhaps I'm getting the point now.
Correct me if I'm wrong
1.JUST BEFORE a new select statement is the right place to do a hard COMMIT
(tiConcurrency)
2.after executing a select you can leave the transaction open for a while.
The timer will shut it down with a hard commit if there is no activity
3.commit retaining during posting is allright because other users will see
the changes you made immediately
(if the other users COMMIT before SELECT)
4.if you try to update a record already changed by an other user you will
get an error message
This means....
using tiConcurrency seems to be a way to be sure your record is the most
recent version. If not you'll get an error message.
Leon