Use case: I've applied an update to the Master that changed the DB structure. I want to apply those changes to all the effected slave sites in one step without having to access individual slave sites.

Requirements (interface details are for example clarity):

- I analyze the db changes and develop the necessary sql to change a single slave site's DB structure. (backup data, change table, restore/transform data, etc)
- Put specific key-word place holders in the sql for things like table prefix
- Open Tools-Database Update tab in JMS component on Master
- Select slave sites to apply changes to
- Paste sql into interface or point to local/remote file containing sql
- Run the scripts against all selected DBs
- Provide detailed success/failure/logging feedback

OK, I have noticed that as a potential requirement for the future.

Just curious if this made it to your road map. I still have issues with database change propagation, so looking for some automation. Will open a new thread for an issue I "think" I am having.

I am patient though.

For your information, in JMS 1.3.x, a new "maintenance" menu is available and allow checking the DB and apply the fixes.

The idea of this new "maintenance" menu is to perform DB verification and compare DB datamodel schema with an expected version.

It extends the joomla 2.5 "extrension manager" / database / fix API with plenty of new things.

sweet

Follow-up for some detail. I understand that you are still working on 1.3 and probably do not want to commit to specific functionality prior to release, but will ask for some guidance anyway.

Based on your explanation it will compare and "sync" database schemas. Considering the ramification, I don't expect it to compare data. This causes some issue when the data changes and is used for compatibility checking. Example would be version numbers etc.

This may be way out there, but can you capture and log the non-read SQL and dump to file for us to analyze during our upgrade testing? Currently I export the database before and after a series of upgrades in my test environment to ensure I don't have any significant issues.

This would nicely round out your new maintenance menu I would think.