Re: an interesting lockRowComparingAttributes:
Re: an interesting lockRowComparingAttributes:
- Subject: Re: an interesting lockRowComparingAttributes:
- From: David Avendasora <email@hidden>
- Date: Wed, 2 Apr 2008 13:38:22 -0400
Couldn't this be the same problem though? 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?
Maybe log the SQL and then compare what WO is looking for with what is
actually in the DB?
Dave
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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden