from the EOModelGroup docs:
The default model group contains all models for an application, as
well as any frameworks the application references. It is automatically
created on demand. The entity name space among all of these models is
global; consequently, the same entity name shouldn't appear in any two
of the models. All cross-model information is represented in the
models by entity name only. Binding the entity name to an actual
entity is done at run-time within the EOModelGroup.
so rather than using the default group you could programatically
create a model group for each model. i believe you can then access
each model from within your app, but you can't create relationships
between the models because they are in different groups. this of
course presumes you have the common entities in different packages. if
you are using the default package, well, you shouldn't be :-)
Note i'm no expert on this - i've little experience with multiple
models in one app - but i'm sure someone will correct me if i'm
talking rubbish :-)
Simon
On 27 Mar 2008, at 08:57, David Griffith wrote:
However, it transpires that both models have a couple of entity
names in common. I can understand why this would cause a problem,
what I need to know is if there is a way around this without having
to completely rename the entities in one of the models.
_______________________________________________
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 [EMAIL PROTECTED]
