• 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
Re: snapshot
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: snapshot


  • Subject: Re: snapshot
  • From: "Jonathan Fleming" <email@hidden>
  • Date: Tue, 11 Feb 2003 23:52:51 +0000

If you don't mind Jonathan, just so i can use it for future ref., what are the sorts of problems you come across when using owns destination relationships.

Jonathan :)





From: Jonathan Rochkind <email@hidden>
To: Art Isbell <email@hidden>, email@hidden
Subject: Re: snapshot
Date: Tue, 11 Feb 2003 11:22:21 -0600

Others disagree with me, but me, I avoid 'owns destination' relationships like the plague. They cause me nothing but trouble. Like I said, others seem to use the feature without problems, but myself, I have a lot less headaches without ever checking 'owns destination'. [Except maybe in many-to-many join tables created by EOModeler---I forget if EOModeler creates relationships in this situation with an 'owns relationship', but if it does, I leave them alone. I just use what EOModeler gives me from the 'join in many-to-many' command.]

--Jonathan

At 05:19 PM 2/10/2003 -1000, Art Isbell wrote:
On Monday, February 10, 2003, at 06:50  AM, Jonathan Fleming wrote:

Any ideas why I may have got this error:

Error: java.lang.IllegalStateException
Reason: Encountered a newly inserted EO with an owns desstination relationship but no snapshot.

A clue is that problem involved a relationship with the "Owns Destination" property set. These aren't common in many eomodels, so this should help narrow down the possibilities. An "Owns Destination" property means that the destination object can't exist without being in a relationship. So if such an object is removed from a relationship but not placed in another relationship by the time its editing context is sent a saveChanges() message, the destination object will be deleted from the DB automatically.


It's not clear to me from the error message whether the source or destination object has no snapshot. But a newly-inserted object won't have a snapshot until it has been saved to the DB, so I'm guessing that the destination object has no snapshot.

Because you know what operations occurred prior to this exception, you should be able to make some educated guesses about why it occurred and test these guesses by changing the operations.

Art
http://homepage.mac.com/aisbell/
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


_________________________________________________________________
Stay in touch with MSN Messenger http://messenger.msn.co.uk
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: snapshot
  • Next by Date: Re: Information: WO 5.2 migration
  • Previous by thread: Re: snapshot
  • Next by thread: Re: snapshot
  • Index(es):
    • Date
    • Thread