I use a to-many to an intermediate EO, then a to-one from it to ERAttachment.
Job ->> Attachment -> ERAttachment This allows the collection of additional metadata and for me simplifies the model. You can also model the to-many directly and turn off the back relationship if you wish. This will create it without modifying the ERAttachment model. David On 2010-09-16, at 12:21 PM, Theodore Petrosky wrote: > How do you model a to many relationship with ERAttachmentMigration? > > I have 1 job and I need to model many attachments. What do I create in the > migration? Obviously, I am not adding an id to the t_job table. Sorry if it > sounds basic but the example only shows a to one relationship. > > Ted > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
