Next message: tnaki..ofthome.net: "calling stored procedures"
- Previous message: Tore Halset: "Re: Testing ExpressionFactory for null values"
- Next in thread: Andrus Adamchik: "Re: transactions, row locking, race condition?"
- Reply: Andrus Adamchik: "Re: transactions, row locking, race condition?"
- Reply: Gentry, Michael \(Contractor\): "RE: transactions, row locking, race condition?"
- Reply: Gentry, Michael \(Contractor\): "RE: transactions, row locking, race condition?"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
The problem: N concurrent users access try to read and modify M table
rows and no two users should get the same table row (using Postgre 8).
I'm certain this must have been mentioned before so I'd appreciate a
link or two to get me started. A couple of comments of what can and
cannot be done in cayenne would be a bonus, but is not required. :)
I could probably write a procedure (though I'm new to pl/pgsql), execute
the sql in a transaction and have it done and over with, but I'd prefer
to do it the "cayenne way". :)
TIA,
Tomislav
- Next message: tnaki..ofthome.net: "calling stored procedures"
- Previous message: Tore Halset: "Re: Testing ExpressionFactory for null values"
- Next in thread: Andrus Adamchik: "Re: transactions, row locking, race condition?"
- Reply: Andrus Adamchik: "Re: transactions, row locking, race condition?"
- Reply: Gentry, Michael \(Contractor\): "RE: transactions, row locking, race condition?"
- Reply: Gentry, Michael \(Contractor\): "RE: transactions, row locking, race condition?"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
This archive was generated by hypermail 2.0.0
: Sat Apr 09 2005 - 10:17:49 EDT