Hi Susanne, For simplicity and backwards compatibility it is not hard to see that the addition of a schema property isn’t adequate. The externalName (Table Name in Entity Modeler) property is enough for the issue of getting the schema name.
Angelo > Em 05/05/2015, à(s) 05:20, Susanne Schneider > <[email protected]> escreveu: > > Hello Angelo, > > we use multiple database schemes all the time and even more most of them are > only known at runtime. We stick to the external name of the entities to add > the schema names in front of the table names. This is done during startup: > all existing eo models are extended that way. > > As we have learned, it is necessary for EOF to have full qualified table > names when building a qualifier for multiple entities of different schemes > (not really surprising if you think about it). > > On the other side the user info dictionary is really quite handy to put info > there: we have all our data model documentation there, besides other info for > special ways of generic entity handling. But thats another story. > > Hope, this info helps you a little bit. > > Best Regards, > Susanne Ângelo Andrade Cirino [email protected] "O homem sensato se adapta ao mundo. O insensato insiste em tentar adaptar o mundo a ele. Todo o progresso depende, portanto, do homem insensato" Sir George Benard Shaw "The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." Sir George Benard Shaw _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
