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