Hi Dietrich,
Dietrich Bollmann wrote:
As this should be a very common situation (different users accessing and
manipulating the same data) I thought there should be a simple
solution :)
What you're describing is, in fact, a very common situation. However,
concurrency issues in general are
Bryce Lohr-2 wrote:
In this case, the easiest thing to do would probably be to cause the DB
to set an exclusive lock on the row with the counter at the time it
reads it. Then, your application can decide if it needs to decrement the
value, delete the row, or whatever, and do the
diresu wrote:
Example:
database state process 1process 2
1 reading 1
1 reading 1
1 adding 1
1
Hi Bill,
Thanks for your reply!
On Wed, 2008-07-16 at 00:20 -0700, Bill Karwin wrote:
diresu wrote:
Example:
database state process 1process 2
1 reading 1
1
Hi,
Here comes a very simple synchronisation question:
I read the paragraph about transaction in the manual
( http://framework.zend.com/manual/en/zend.db.html#zend.db.adapter.transactions
)
but couldn't figure out if a transaction is sufficient to deal with
the following situation:
Different
