Hi Mark, I thought about it too, but it would be a non-standard solution, since each developer could use a name for the property. To be more precise, I abandoned this idea after working to change the FrontBase plug-in and SQLHelper to use EOSchemaSynchronizationFactory. The code that will use the schema name property is so deep down in the Wonder framework that using a non-standard property name could lead to serious problems.
What’s your opinion on the validity of adding the schema name as an explicit property for entities? Is it worth the effort? Angelo > Em 04/05/2015, à(s) 20:53, Morris, Mark <[email protected]> escreveu: > > Don’t forget about the built-in userInfo dictionary in EOEntity (which has > support in Entity Modeler). That seems like a logical place for extra info > like this. > > Regards, > Mark Â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]
