Re: Better key path creation
Re: Better key path creation
- Subject: Re: Better key path creation
- From: Mike Schrag <email@hidden>
- Date: Tue, 21 Dec 2010 15:17:02 -0500
this is why i didn't go down this path originally ... i think you can reuse instances if you write the templates carefully (the key instance returned from a relationship can be the same as the key instances of the destination entity), but it just made me nervous about the amount of "stuff" it was generating. plus if you have a lot of eo's, which some places definitely do, you end up creating a LOT of extra classes, and as someone in the thread mentioned, i got concerned about permgen space if you're talking about dumping an extra 3000 or whatever classes into your hierarchy.
ms
On Dec 21, 2010, at 3:02 PM, Ramsey Gurley wrote:
> Thinking out loud...
>
> It would be interesting to see how much memory the vars approach uses... Not only does each EO get an instance, but each relationship gets a new instance of the ERXKey subclass too... which in turn has its own relationships and new instances. It's certainly easier to read, but that looks like it may grow exponentially and run out of memory with large models. :-/
>
>
> On Dec 21, 2010, at 2:28 PM, Ramsey Gurley wrote:
>
>> Awesome. I like that best.
>>
>> Ramsey
>>
>> On Dec 21, 2010, at 1:03 PM, Timo Hoepfner wrote:
>>
>>> Or we use vars instead of methods:
>>>
>>> MovieRole.pathTo.talent.photo.photo.key()
>>>
>>> Adding a patch in a minute...
>>>
>>> Timo
>>>
>>>
>>> Am 21.12.2010 um 18:32 schrieb Timo Hoepfner:
>>>
>>>>> Does this still produce the collisions that Timo observed? If so, I know it isn't pretty, but I think the patch may stand a better chance if it has a prefix like
>>>>>
>>>>> MovieRole.$path.$talent().$photo().$photo().key()
>>>>>
>>>>> Otherwise, the next time someone wants to add a new method to ERXKey, the change is going to be subject to everyone getting upset because it brakes with their model. But then, I also remember Mike saying something about perm cache at some point in time...
>>>>>
>>>>
>>>> I like it. Didn't know $ would be allowed within a var name. Looks like € would also be allowed. :)
>>>>
>>>> I've added a path to the (WOLips) ticket that does so and also allows to specify a userInfo entry on a relationship to fall back to plain ERXKeys for it (when the target Entity doesn't use "extended ERXKeys").
>>>>
>>>> http://issues.objectstyle.org/jira/browse/WOL-1189
>>>>
>>>> Timo
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>
> _______________________________________________
> 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
_______________________________________________
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