I've added both the MySQL and Oracle model and I now get this error:
Database error while fetching [...] object: The model 'DynEd-
Oracle' (path: file:[...]/DynEd-Oracle.eomodeld) has an entity name
conflict with the entities ([...]) already in the model group
<EOModelGroup (("DynEd-MySQL", "file:[...]/DynEd-MySQL.eomodeld"))>
So having both models in the build will cause issues.
On Aug 13, 2009, at 12:14 PM, Ray Kiddy wrote:
> It may be simpler to have code that grabs the correct model, adds it
> to an EOModelGroup and then sets the default EOModelGroup to that
> group.
What did you mean with 'grab' ?
> As far as I can remember, If this is done in the Application
> constructor, the EO-level initialization will still happen correctly.
Thanks
kib
"Success is not final, failure is not fatal: it is the courage to
continue that counts."
Winston Churchill
Klaus Berkling
Web Application Dev. & Systems Administrator
DynEd International, Inc.
www.dyned.com | www.eskimo.com/~kiberkli
This archive was generated by hypermail 2.0.0 : Thu Aug 13 2009 - 17:52:23 EDT