On Wed, Feb 22, 2006 at 09:21:04PM -0500, Daniel Convissor wrote:
Ouch. Let's see if I can do something about that...
My thought is to run the upgrade once. Have the process obtain all of the prefix names by parsing all the sites/settings.php files up front. I do something along these lines in the Database Table Creation Script:
http://drupal.org/files/issues/create.php.v2.txt http://drupal.org/node/20530
Was hoping for a little feedback from folks here on that idea. Uh, okay, no takers yet, so let me be more direct. :) * Are the core developers interested in having multi-site support in the update process? (I mean, why work on something just to have it go nowhere, right?) * What do you think is a better/more workable/more Drupal-like approach: a) put an option in the process that the user can select (in update_selection_page(), I guess) that tells the system to update all tables in the database, not just those for the present site. b) an option for the user to say whether to update the shared tables or not. This way, the user will update each site in each site's interface, but the user will only select the shared table run one time. c) other ideas? Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409