A good way would be to put your EOModel into a framework and include it in both projects on your class path. The corresponding migrations are inside the framework too and as the current db schema version is held inside the db only one of both projects would update the db.
jw Am 26.08.2011 um 09:53 schrieb Theodore Petrosky: > How do youse guys handle multiple projects that may access the same data (or > subsets). > > I have an app that manages users information at the company. (People with > various meta data). Recently, one of the managers asked to create an app that > shows at a glance a subset of the data. > > So I thought I would have to create a new app that was real simple (no log in > as it is only available inside the subnet). But then I had to make a change > to the data structure (I use migrations so I have no problem there). Now I > have to update two project's EO Models. I will only do the migrations from > one project. > > There must be a better way. > > How do youse guys handle this? > > Ted > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
