• 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: Multiple model approach
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple model approach


  • Subject: Re: Multiple model approach
  • From: Chuck Hill <email@hidden>
  • Date: Mon, 16 May 2005 09:49:20 -0700

I do this all the time. Relationships across models are not a problem. It all works fine, other than when sub-classing across models. EOModeler has some bugs related to that. What I do is to subclass in the same model as the parent, and then cut and paste it into the intended model. IIRC, you need to manually recreate any relationships.


Chuck


On May 14, 2005, at 2:57 PM, Florijan Stamenkovic wrote:

Hi.


I am working on an app that will end up with a large number of tables. It consists of some tables (the Project table for example) that are related to just about every other major table, but have no knowledge about them. They have (the super tables) to-many relationships towards them though. Those other major tables have knowledge of those super-tables (foreign keys), but in general not much about each other. And then there are number of helper-tables (for constant values for example) that are typically related to only one major table.


This would be a lot more easy to organize if I would separate all those major tables (with their belonging helper-tables) into separate models, and link them through the model group to the super-tables. Basically to apply the relations in reality also to the model group.

I've been reading a lot about the EOF stack and how data is fetched, but can't really get my head around it all at once. As I see it using multiple models should not be an issue for it since I would still be using just one stack, right?

However, I did see some issues rising over just adding the models to a project (XCode, don't know how Eclipse is on that at all), and that made me think that it is not a typical approach to take. Or no?

Anybody has some practical experience or advice on the issue in general?

Flor

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net


This email sent to email@hidden

--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development 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


References: 
 >Multiple model approach (From: Florijan Stamenkovic <email@hidden>)

  • Prev by Date: Re: long running task
  • Next by Date: Re: Webobjects 5.2.4 and JAI
  • Previous by thread: Re: Multiple model approach
  • Next by thread: long running task
  • Index(es):
    • Date
    • Thread