• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: an interesting lockRowComparingAttributes:
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: an interesting lockRowComparingAttributes:


  • Subject: Re: an interesting lockRowComparingAttributes:
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 2 Apr 2008 10:19:10 -0700


On Apr 2, 2008, at 4:30 AM, David Avendasora wrote:

The fact that Chuck didn't come up with this makes me doubt my memory, but...

It seems that when I've run into this in my applications, it usually means that between the time the EO was read out of the database, and the time it is written back in, something in one of the locking fields changed, or the field isn't "locking-friendly" in that WO has a difficult time reading the datatype of the DB field and converting it into the requested Java datatype and then converting it back and coming up with the original value. I know with MS SQL Server that long text fields are a problem.

I _believe_ (please correct me if I'm wrong) when EOF does an update, it does it along the lines of "UPDATE TABLE WHERE ATTRIBUTE_1 = x, ATTRIBUTE2 = y, etc" where the attribute values are from the original reading of the record.

The problem is that the UPDATE can't find any records matching the original attributes, and therefore didn't "select" any rows for updating.

Dave

On Apr 1, 2008, at 6:06 PM, Johan Henselmans wrote:

Error:
com.webobjects.eoaccess.EOGeneralAdaptorException: lockRowComparingAttributes -- com.webobjects.jdbcadaptor.JDBCChannel: lock operation failed to select any rows


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.

That said, I think that we did look at a case where you had this problem. I just can't recall what the cause 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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: an interesting lockRowComparingAttributes:
      • From: David Avendasora <email@hidden>
References: 
 >an interesting lockRowComparingAttributes: (From: Johan Henselmans <email@hidden>)
 >Re: an interesting lockRowComparingAttributes: (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: WO 5.4 Linux Deployment
  • Next by Date: Re: Locking Session.defaultEditingContext() Question
  • Previous by thread: Re: an interesting lockRowComparingAttributes:
  • Next by thread: Re: an interesting lockRowComparingAttributes:
  • Index(es):
    • Date
    • Thread