Re: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
Re: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
- Subject: Re: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
- From: OC <email@hidden>
- Date: Thu, 05 Feb 2015 13:12:30 +0100
Dave,
On 5. 2. 2015, at 12:50, David Avendasora <email@hidden> wrote:
> When you look for the row and find it, are you using the *exact* same SQL that EOF did (gotten from the adaptor logging)?
Alas, adaptor logging has not been switched on when the problem occurred.
I've tried to switch in on now and try to open the same page as has been opened before, but ... in vain? I must have lost my track; I've though to switch the logging on one sets up
log4j.category.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG
in Properties, but that does not seem to log anything. I've even tried to run an instance afresh with this setting (and just to be triple sure, also with the good ole -EOAdaptorDebugEnabled YES), both in vain. What's the right trick to switch the logging on?
Thanks a lot,
OC
>> On Feb 5, 2015, at 6:19 AM, OC <email@hidden> wrote:
>>
>> Hello there,
>>
>> well I must have some pretty weird bug somewhere. Does anybody have any idea what dumb fault of mine might cause
>>
>> ===
>> Caused by: com.webobjects.eoaccess.EOObjectNotAvailableException: prepareForSaveWithCoordinator: Cannot save the object with globalID _EOIntegralKeyGlobalID[DBDFPrototype (java.lang.Integer)1000022]. The row referenced by this globalID was missing from the database at the time a fetch was attempted. Either it was removed from the database after this application got a pointer to it, or there is a referential integrity problem with your database. To be notified when fetches fail, implement a delegate on EODatabaseContext that responds to databaseContextFailedToFetchObject().
>> at com.webobjects.eoaccess.EODatabaseContext.prepareForSaveWithCoordinator(EODatabaseContext.java:5657)
>> at com.webobjects.eocontrol.EOObjectStoreCoordinator.saveChangesInEditingContext(EOObjectStoreCoordinator.java:370)
>> at com.webobjects.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3192)
>> at er.extensions.eof.ERXEC._saveChanges(ERXEC.java:1179)
>> at er.extensions.eof.ERXEC.saveChanges(ERXEC.java:1102)
>> at er.extensions.eof.ERXEC$saveChanges$8.call(Unknown Source)
>> at cz.ocs.model.OCSEnterpriseObject._saveTolerantlyChangesInEC(OCSEnterpriseObject.groovy:520) // ec.saveChanges()
>> ===
>>
>> given the appropriate row definitely does exist in the database? (I have checked and re-checked; it is there, and it has still its original creation timestamp two-odd years old.)
>>
>> Thanks for any insight,
>> OC
>>
>>
>> _______________________________________________
>> 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
>
>
> —————————————————————————————
> WebObjects - so easy that even Dave Avendasora can do it!™
> —————————————————————————————
> David Avendasora
> Senior Software Abuser
> Nekesto, Inc.
>
>
>
>
>
>
_______________________________________________
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