On Apr 2, 2008, at 2:18 PM, Art Isbell wrote:
On Apr 2, 2008, at 7:38 AM, David Avendasora wrote:
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, but I think Chuck's point is that SELECT ... FOR LOCK
shouldn't be generated unless the fetch specification was configured
to lock objects (i.e., fetchSpec.locksObjects() returns true). This
is not recommended.
Yes. And there is at least one place in EOF where an unexpected
exception or null or something, causes it to assume that it is a lock
operation. I _think_ it has something to do with adaptor operations.
I just can't quite recall what it was.
Chuck
--
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]
