On Apr 2, 2008, at 10:38 AM, David Avendasora wrote:
Couldn't this be the same problem though?
No. :-)
If the SELECT ... FOR LOCK can't find any rows that have fields with
values that match exactly with what the DB has, then it wouldn't get
any rows either. No?
Yes, but... SELECT ... FOR LOCK is _pessimistic_ locking and EOF
should be using optimistic locking. If EOF is issuing pessimistic
locking SQL, then something has gone wrong.
Maybe log the SQL and then compare what WO is looking for with what
is actually in the DB?
That is not the issue. The important symptom is that EOF is doing a
SELECT ... FOR LOCK.
Didn't you see this when you were using <cough> Vertical Inheritance?
Chuck
On Apr 2, 2008, at 1:19 PM, Chuck Hill wrote:
Close, but no rabbit stamp. What you are talking about produces an
optimistic locking expection and "update operation failed to update
any rows" from the channel. What Johan is hitting is an SQL
statement like SELECT ... FOR LOCK. That is pessimistic locking.
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
