Re: faulting relationship problem
Re: faulting relationship problem
- Subject: Re: faulting relationship problem
- From: Michael Gargano <email@hidden>
- Date: Mon, 22 Aug 2011 13:18:10 -0700
- Acceptlanguage: en-US
- Thread-topic: faulting relationship problem
On Aug 22, 2011, at 4:02 PM, Chuck Hill wrote:
>
> On 2011-08-22, at 8:13 AM, Michael Gargano wrote:
>
>> Just the default constructor, which implicitly calls super. All the model classes are EOGenerated. Any other ideas to check?
>
> Awake from insertion?
Checked it, looks good. The weird thing is I'm doing these cascaded popups all over and they seem fine except on this form. This is a modal dialog on top of a modal dialog, so this is a child EC, but the fetches are into the child EC so there shouldn't be a problem. I'll keep searching, I'll update the list when I find something.
> Bad modelling.
How dare you sir! :-p
> Are you using inheritance and have duplicate PKs in different tables? All the entities in an inheritance hierarchy MUST have a PK unique across all tables.
>
I am using inheritance, but it's single table inheritance (learned that one pretty early on).
>
>> On Aug 19, 2011, at 3:39 PM, Chuck Hill wrote:
>>
>>> Sounds like you forgot to call super someplace in your EOs.
>>>
>>>
>>> On 2011-08-19, at 12:27 PM, Michael Gargano wrote:
>>>
>>>> Hi all,
>>>>
>>>> I have cascading popup buttons that are narrowing down to a particular instance of an entity and one of the popups is populated with the field from a relationship on that entity.
>>>> So, the fetch spec. has a qualifier consisting of the values of all the previous choices and it retrieves the narrowed set of objects. Next, I iterate through the results adding the object from the relationship to a NSMutableArray for display. It is at this point that, periodically, the relationship returns null instead of the object. This is a test system so there is only one entity in the database and this relationship should definitely return an item. If I do this in reverse... I preform the fetch on the relationship's entity and use key paths in the qualifier back to the master entity it seems to go away (this is hideous).
>>>>
>>>>
>>>> So, to sum it up... even though the fetch returns the correct results, it seems the proxy load of the relationship slave entity sometimes fails.
>>>> This is on a PostgreSQL DB, btw.
>>>>
>>>> Has anyone ever seen issues when faulting objects from a relationship? Is it not guaranteed to return an object even if the inner join is definitely valid?
>>>>
>>>>
>>>> Thanks.
>>>> -Mike
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>> --
>>> Chuck Hill Senior Consultant / VP Development
>>>
>>> Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
>>> http://www.global-village.net/products/practical_webobjects
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
> --
> Chuck Hill Senior Consultant / VP Development
>
> Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
> http://www.global-village.net/products/practical_webobjects
>
>
>
>
>
>
>
>
_______________________________________________
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