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: Brendan Duddridge <email@hidden>
- Date: Thu, 19 May 2005 22:12:18 -0600
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.
Thanks,
________________________________________________________________________
_
Brendan Duddridge | CTO | 403-277-5591 x24 |
email@hidden
ClickSpace Interactive Inc.
Suite L100, 239 - 10th Ave. SE
Calgary, AB T2G 0V9
http://www.clickspace.com
_______________________________________________
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