You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cayenne.apache.org by Mike Kienenberger <mk...@gmail.com> on 2006/04/14 20:35:23 UTC

FaultFailureException on record that exists...

Andrus, do you think that this is another symptom of the ObjectId
comparisons?   I'm in the process of upgrading to the latest cvs to
test it again, but this error is from cvs 2006-04-12 1400 EST.

Note that the record (Id = 7) is fetched (returned 1 row), then a
FaultFailureException is thrown for it.

Anmt INFO  [SocketListener0-1 04-14 14:28:02] QueryLogger: SELECT
t0.IS_ACTIVE, t0.NAME, t0.ID FROM ADMINDB.SEC_SYSTEM t0 WHERE t0.ID =
? [bind: 7]
Anmt INFO  [SocketListener0-1 04-14 14:28:02] QueryLogger: ===
returned 1 row. - took 0 ms.
Anmt INFO  [SocketListener0-1 04-14 14:28:02] QueryLogger: +++
transaction committed.

Caused by: org.objectstyle.cayenne.FaultFailureException: [v.1.2-dev
April 12 2006] Error resolving fault, no matching row exists in the
database for ObjectId: <ObjectId:SecSystem, ID=7>
	at org.objectstyle.cayenne.access.DataContext.prepareForAccess(DataContext.java:1753)
	at org.objectstyle.cayenne.CayenneDataObject.readProperty(CayenneDataObject.java:238)
	... 69 more

Re: FaultFailureException on record that exists...

Posted by Mike Kienenberger <mk...@gmail.com>.

On 4/14/06, Mike Kienenberger <mk...@gmail.com> wrote:
> Andrus, do you think that this is another symptom of the ObjectId
> comparisons?   I'm in the process of upgrading to the latest cvs to
> test it again, but this error is from cvs 2006-04-12 1400 EST.
>
> Note that the record (Id = 7) is fetched (returned 1 row), then a
> FaultFailureException is thrown for it.

The answer appears to be yes -- this was the cause of my
FaultFailureException.   At least, I'm not getting now that I upgraded
to the ObjectId fix.