Multiple model approach
Multiple model approach
- Subject: Multiple model approach
- From: Florijan Stamenkovic <email@hidden>
- Date: Sat, 14 May 2005 23:57:25 +0200
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:
This email sent to email@hidden