Re: Changing path to alternative EOModels

From: Chuck Hill (chil..lobal-village.net)
Date: Thu Aug 13 2009 - 18:26:34 EDT

  • Next message: Lachlan Deck: "confluence / jira down on objectstyle?"

    On Aug 13, 2009, at 2:51 PM, Klaus Berkling wrote:

    >
    > 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.

    Yes, you will need to have them somewhere that NSBundle won't find them.

    > 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' ?

    Load it from where NSBundle is not seeing it. :-)

    Cough. Prototypes. Cough.

    Chuck 

    -- 
Chuck Hill             Senior Consultant / VP Development

    Practical WebObjects - for developers who want to increase their  
overall knowledge of WebObjects or who are trying to solve specific  
problems.
http://www.global-village.net/products/practical_webobjects

    This archive was generated by hypermail 2.0.0 : Thu Aug 13 2009 - 18:27:24 EDT