• 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
followup: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

followup: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist


  • Subject: followup: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
  • From: OC <email@hidden>
  • Date: Thu, 05 Feb 2015 12:22:30 +0100

Sorry I've sent too soon; I wanted to add...

On 5. 2. 2015, at 12:19, OC <email@hidden> wrote:
> 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.)

... that I have bumped into similar problem before, and we have suspected it was caused by superfluous (and probably harmful) object locking. No locks in there anymore, I've removed them:

http://prod.lists.apple.com/archives/webobjects-dev/2015/Jan/msg00161.html

Thanks,
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


  • Follow-Ups:
    • Re: followup: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
      • From: Ramsey Gurley <email@hidden>
    • Re: followup: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
      • From: Chuck Hill <email@hidden>
References: 
 >prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist (From: OC <email@hidden>)

  • Prev by Date: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
  • Next by Date: Re: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
  • Previous by thread: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
  • Next by thread: Re: followup: prepareForSaveWithCoordinator: Cannot save the object with globalID / row does exist
  • Index(es):
    • Date
    • Thread