Subject | Re: [IBO] concurrency locking and IBO-defaults |
---|---|
Author | L.M. Bemmelmans |
Post date | 2003-07-21T15:28:27Z |
Helen,
Thank you for replying and for sharpening my remarks. They are not allways
accurate.
I understand how readcommitted works and I understand the way IBO works with
this:
-autocommit = true
-commitretaining to commit changes while continuing the same transaction
-timerfunction of TIB_transaction to do a hard commit every x minutes.
I also understand tiConcurrency, but I don't know how to work with IBO using
this, in combination with user-interfacing:
1. user A makes a selection of records ---> so no commit after select as you
suggested
2. user B makes the same selection ---> also without committing after
selecting
3. user A changes one record, and I want other users to see changes
immediate ---> so now I need a hard commit
put in the afterpost event of TIBOquery ?
4. user B makes the same selection again....but does not see the changed
records of user A.
It seems he first has to COMMIT and then start the selection again to see
the changed record.
That's why I stated that after every select I need a hard commit, to be sure
user B sees all changes made to the database.
But you say it is not wise to commit after each select. Now I'm lost on that
one. That's why I stick to tiCommitted at the moment.
Leon
Thank you for replying and for sharpening my remarks. They are not allways
accurate.
I understand how readcommitted works and I understand the way IBO works with
this:
-autocommit = true
-commitretaining to commit changes while continuing the same transaction
-timerfunction of TIB_transaction to do a hard commit every x minutes.
I also understand tiConcurrency, but I don't know how to work with IBO using
this, in combination with user-interfacing:
1. user A makes a selection of records ---> so no commit after select as you
suggested
2. user B makes the same selection ---> also without committing after
selecting
3. user A changes one record, and I want other users to see changes
immediate ---> so now I need a hard commit
put in the afterpost event of TIBOquery ?
4. user B makes the same selection again....but does not see the changed
records of user A.
It seems he first has to COMMIT and then start the selection again to see
the changed record.
That's why I stated that after every select I need a hard commit, to be sure
user B sees all changes made to the database.
But you say it is not wise to commit after each select. Now I'm lost on that
one. That's why I stick to tiCommitted at the moment.
Leon