speleo wrote:
I'd like to see the upgrade routine simplified by removing the requirement to edit the configure.php file to prevent the db from being recreated. I suspect a few lines of code to check for the existence of the db tables would be all that is required. A new install would create the tables but an upgrade would leave them alone.
Similarly, it should be possible to identify if a schema update is required and flag the right file to run.
Also, it would be nice if the upgrade automgically cleared the session and cache directories / files.
This seems to be more a framework level issue, where the component installer should give the user a choice between upgrade and new install. upgrading also involves messing with the db to upgrade the schema etc and it is dangerous to do so without appropriate backups etc. (people in general dont follow instructions and are likely to shoot themselves in the foot etc)
I suspect we'll build an upgrade path within CiviCRM in the not so distant future
lobo