Let me be more clear.
It is possible to run migrations automatically but the different databases (whose connection dictionary is only known inside a session) will not all be automatically updated.
I have migrations turned on and automatically connecting to (and updating) an empty database that is the same structure as all the session specific databases. Right now, the management of the per-session database schemas is a combination of perl and groovy. This works pretty well (if sort of inelegantly)
I do have a partially completed feature that will give me more consistent manageability. The feature is intended to allow web administration of new databases (create a new database on one of the available servers, run migrations, profit). This will necessarily require more control over migrations so although I am concerned about completely automatic migrations in this situation, with the right balance of feedback and control (and good backups) I'm going to release this to the client configuration folks so they can turn up a client environment more easily.
On Jun 18, 2012, at 5:04 PM, Larry Mills-Gahl wrote: Not automatically. Migrations happen during the application startup and at that point, they have default connection dictionary information. I do use migrations but that just migrates the common databases and an empty stub database (that uses the default connection dictionary) on the main db server. Using that empty stub means that I don't have to worry about loading and unloading different model groups. If you aren't connected to a particular facility db, you are connected to the stub and EO is happy about all the objects, you just don't have any data.
I have some old perl that will iterate through the active databases to check schema consistency.
When I have extra time (come on ... stop laughing!!) finishing the utility to trigger migrations across active databases is on the list of things to do. Right now it's not an urgent or consistent issue so it doesn't get top priority.I haven't made this completely automatic (because I'm chicken and have an allergy to injecting lead into my own foot)
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|