I've done some testing now, the dbSync calls incur very little overhead
with regards to the telling/updating mechanism of objects in other
processes.
What I still don't understand then is the ability to lock only certain
files in the dbSync call when the dbSync call is doing a global block in
On Sun, Jan 06, 2013 at 01:33:55AM +0700, Henrik Sarvell wrote:
In which actual situations do you need to do dbSync - commit upd as
opposed to just commit upd? It seems to me the RMDBS equivalent is begin -
commit?
The sequence
(dbSync) - (modify objects) - (commit 'upd)
is all and only
Yes, but the caching issue is not resolved. If two processes increment
the object's counter, the second one will still hold the old
un-incremented value, because it didn't wait to receive the changes
broadcasted by (commit 'upd). This waiting is handled by the 'sync' call
in (dbSync).
I'm
OK so how would you deal with a situation where you have the need to
quickly increment people's balances like I mentioned previously but at the
same time you have another process that has to update a lot of objects by
fetching information from many others?
This second process will take roughly
On Sun, Jan 06, 2013 at 08:00:51PM +0700, Henrik Sarvell wrote:
OK so how would you deal with a situation where you have the need to
quickly increment people's balances like I mentioned previously but at the
same time you have another process that has to update a lot of objects by
fetching
How does the GUI framework work?
What if user A pulls upp object X in an update form and then goes to the
toilet and in the meantime user B pulls the same object and changes it,
will user A see any changes when he comes back?
On Sat, Jan 5, 2013 at 10:48 PM, Alexander Burger
On Sat, Jan 05, 2013 at 11:25:30PM +0700, Henrik Sarvell wrote:
How does the GUI framework work?
What if user A pulls upp object X in an update form and then goes to the
toilet and in the meantime user B pulls the same object and changes it,
will user A see any changes when he comes back?
In which actual situations do you need to do dbSync - commit upd as
opposed to just commit upd? It seems to me the RMDBS equivalent is begin -
commit?
If you do db, put and commit upd calls so that they happen roughly at the
same time you should be as safe as you are when you do a update table
