Hello Andri;
I'm not sure I follow precisely what you're after, but I had a problem
where a very large volume of concurrent writes into a database product
from a number of instances was causing deadlocks, so I subclassed the
EOF JDBC Adaptor to apply ordered table-level locks on the leading
edge of the transaction. This has worked out very well and has been
in production for some time. You can get the source code for this
with my framework and maybe something like this may be what you are
after.
cheers.
a EOFetchSpecification that locks objects and throws an exception on
any other access trials (SELECT, UPDATE, whatever) is required. The
behaviour should be the same as the SQL Statement 'SELECT FOR UPDATE
NO WAIT'.
...
Any helpful hints or examples how to use 'setUseNoWaitLocks' would
be appreciated.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
