Re: Trying to clear a dead-lock of some type
Re: Trying to clear a dead-lock of some type
- Subject: Re: Trying to clear a dead-lock of some type
- From: Chuck Hill <email@hidden>
- Date: Fri, 20 May 2005 10:01:28 -0700
On May 19, 2005, at 9:12 PM, Brendan Duddridge wrote:
Sacha,
This is one error, a frustrating one. I'm locking the rows in the EO
model
in just about every possible way, including the Pkey. What's the
real
secret to this one?
com.webobjects.eoaccess.EOGeneralAdaptorException:
updateValuesInRowDescribedByQualifier --
com.webobjects.jdbcadaptor.JDBCChannel: method updated 2 rows, it is
only
permitted to update 1 row
Something is very wrong there. Very wrong indeed. Turn on SQL
logging
and look at the statement that caused that error.
Chuck
Funny, but we had this error just the other day. Turns out a plain
many-to-many join table in our FrontBase 4.1.16 database had duplicate
rows, even though there was a compound primary key defined on the only
two columns that was supposed to prevent this. We have no idea how the
duplicate rows got in there.
We deleted the duplicates, dropped the primary key, re-created the
primary key and the problem so far has gone away.
Yike! Did you report that to FrontBase? Were you running the database
without a license? IIRC, it does not perform some checks without a
some sort of license in place.
Chuck
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development 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