• 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: Inheritance and relationships
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inheritance and relationships


  • Subject: Re: Inheritance and relationships
  • From: David LeBer <email@hidden>
  • Date: Fri, 8 Aug 2008 21:31:04 -0400


On 8-Aug-08, at 7:53 PM, Guido Neitzer wrote:

On 08.08.2008, at 15:11, Chuck Hill wrote:

Hmmm. Back to the old application, FETCHING works now. Resolving a relationship to an object that was NOT cached earlier, crashes.

When I do a fetch, the relationship is resolved just fine when the object the relation is pointing to was fetched before. But it stops working as soon as the timestamp lag is reached.

Weird.

What glorious fun for a Friday!

This is sounding more like a variant of the problem Mike worked on in Wonder: if you fetch the object, the GID is set correctly. If a relationship is followed, it is set incorrectly. This is a total guess.

But it sounds like the thing I'm seeing. And I didn't have time exploring that much. Just switched to that workspace a couple of times when I thought I had an idea. But I was at the office today so I didn't have much time for tinkering with it.


At least I'm down to the following scenario:

1. Fetching the stuff with a normal fetch works now.

2. Following a relationship does not work, if I haven't fetched that object at the end of the relation before.

After a while I get null values back when I try to access something that follows that relationship - on an object where I got a valid value back before. Very, very weird!

I saw these exact symptoms when trying to use Wonders ERAttachment.

My model was from an abstract Product entity to the abstract ERAttachment entity.

I 'resolved' (read: I punted) the issue by modeling directly to the ERFileAttachment entity instead.

;david

--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: 	http://codeferous.com
blog: 	http://davidleber.net
profile:	http://www.linkedin.com/in/davidleber
twitter:	http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org




_______________________________________________ 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
References: 
 >Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Lachlan Deck <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Chuck Hill <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Chuck Hill <email@hidden>)
 >Re: Inheritance and relationships (From: Mike Schrag <email@hidden>)
 >Re: Inheritance and relationships (From: Mike Schrag <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)
 >Re: Inheritance and relationships (From: Chuck Hill <email@hidden>)
 >Re: Inheritance and relationships (From: Guido Neitzer <email@hidden>)

  • Prev by Date: Re: Exception only when framework is embedded
  • Next by Date: Re: Inheritance and relationships
  • Previous by thread: Re: Inheritance and relationships
  • Next by thread: Re: Inheritance and relationships
  • Index(es):
    • Date
    • Thread