This is just off the top of my head, but you _can_ model the toManyThousands 
relationship, just don't make it a class property. Then in the EOGenerator 
template you could get all the toMany relationships that are not class 
properties and generate the code to use ERXUnmodeledToManyRelationship for 
those.

But that assumes that all non-class-property toMany relationships should be 
handled this way...

Dave

On Aug 9, 2011, at 5:32 AM, Ricardo J. Parada wrote:

> Yep, modeling an unmodeled relationship… sounds contradictory.
> 
> I guess in my dream it was really modeled but generated different accessors 
> during EOGenerate.
> 
> :-)
> 
> On Aug 5, 2011, at 11:53 AM, Ricardo J. Parada wrote:
> 
>> Yes, you're right.  :-)
>> 
>> I found ERXUnmodeledToManyRelationship in your presentation but nowhere you 
>> said it was part of entity modeler.  
>> 
>> :-)
>> 
>> 
>> 
>> On Aug 5, 2011, at 10:41 AM, Kieran Kelleher wrote:
>> 
>>> Ricardo,
>>> 
>>> No, you were dreaming.  :-)
>>> 
>>> Regards, Kieran.
>>> (Sent from my iPhone)
>>> 
>>> 
>>> On Aug 4, 2011, at 5:35 PM, "Ricardo J. Parada" <rpar...@mac.com> wrote:
>>> 
>>>> I thought there was something about this in one of the sessions in this 
>>>> WOWODC 2011 but I can't recall.  Something about selecting 
>>>> ERXUnmodeledToManyRelationship in the entity modeler but I don't see it.
>>>> 
>>>> Is there such as thing in entity modeler?
>>>> 
>>>> Thanks,
>>>> Ricardo
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Aug 2, 2011, at 1:02 PM, Jesse Tayler wrote:
>>>> 
>>>>> Ok, I haven't even looked yet -- so excuse if I'm off base --
>>>>> 
>>>>> But shouldn't this be a part of the eo-templates?
>>>>> 
>>>>> Just about every model has this potential problem, so is there a reason 
>>>>> we can't check off a box in the modeler to suggest this is a unmodeled 
>>>>> to-many or something and generate the methods?
>>>>> 
>>>>> Not that making the method is hard or anything, more that it seems like a 
>>>>> solid standard practice that should be elevated in visibility?
>>>>> 
>>>>> 
>>>>> 
>>>>> On Aug 2, 2011, at 12:55 PM, Kieran Kelleher wrote:
>>>>> 
>>>>>> It's easy, …..
>>>>>> 
>>>>>> (1) Copy and paste the example from that 
>>>>>> er.extensions.eof.ERXUnmodeledToManyRelationship class javadoc into 
>>>>>> BBEdit
>>>>>> 
>>>>>> (2) Do some find/replace editing
>>>>>> 
>>>>>> (3) Paste the result into your entity class that needs to have the 
>>>>>> "unmodeled" toMany relationship.
>>>>>> 
>>>>>> (4) Delete the model toMany relationship in the relationships pane in 
>>>>>> the EOModel.
>>>>>> 
>>>>>> Test, and you are done.
>>>>>> 
>>>>>> I have thought about having some user-info entry in the model entity 
>>>>>> that could be used to auto generate this boiler-plate code in the eogen 
>>>>>> superclass, but it just has not been a priority for me.
>>>>>> 
>>>>>> Regards, Kieran
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Aug 2, 2011, at 12:42 PM, Jesse Tayler wrote:
>>>>>> 
>>>>>>> 
>>>>>>> On Aug 2, 2011, at 12:38 PM, Kieran Kelleher wrote:
>>>>>>> 
>>>>>>>> On a related note, with regards tens of millions on one side of a 
>>>>>>>> to-many …. that will kill your performance on saving a change to that 
>>>>>>>> relationship unless you make the relationship a one-sided 
>>>>>>>> relationship. @see er.extensions.eof.ERXUnmodeledToManyRelationship<S, 
>>>>>>>> D> for one solution to that situation. I recommend using an 
>>>>>>>> "unmodeled" toMany for any relationship where the toMany can be in the 
>>>>>>>> thousands. YMMV.
>>>>>>> 
>>>>>>> this is of interest to me --
>>>>>>> 
>>>>>>> any docs or just code to read on this subject?
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>> http://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com
>>>>> 
>>>>> This email sent to rpar...@mac.com
>>>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/webobjects-dev/rparada%40mac.com
>> 
>> This email sent to rpar...@mac.com
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
> 
> This email sent to webobje...@avendasora.com

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to