Re: [phpesp-dev] soma changes

[Franky V. L. <lie...@te...>]

On Sat, 29 Mar 2008 14:58:00 -0400
Matthew Gregg <mat...@gm...> wrote:

> Splitting the file in this way seems reasonable.  Wouldn't we want the
> file names to be *.php, so they can't be accidentally viewable?  And
> since we are renaming, I don't see any reason to keep the phpESP.ini
> name.
> 
> I propose:
> require (config_defaults.php);
> 	==> defaults, gets overwritten every new release
> require (config.php);
> 	==> your own values, never gets overwritten
> require (config_fixed.php);
> 	==> fixed parts, you can change these, but they get
> overwritten

Well, the idea was to make the upgrade as painless as possible, but
then again: what's in a name :) If anybody else doesn't object to a
name change?

> > Now I also plan an easier update:
> > 1) read config files
> > 2) check version of phpesp in db with the one in phpESP.ini.fixed
> >         if version table in db doesn't exist
> > 		==> suggest version=2.0.2, is changeable
> See comment I made about the suggested version in my reply to the SVN
> diff email.

See my reply in private.

> > 	if version table in db exists ==> take that one
> > 3) show a link to take db backup if wanted
> > 4) show a link to execute the update scenario: 2.0.2==>2.0.3,
> > 2.0.3==>2.0.4, ... for this, the update db scripts need to be parsed
> > and the DB prefix added if needed
> > 5) if update ok and tables contain no prefix: show link to script
> > for prefix update, and warns it needs to be changed in the config
> > file when executed
> > 
> > Any comments?
> I like the idea of allowing DB updates inside the application, we just
> need to be darn sure not to destroy anything ;-)

Indeed, but as always: one should always take a backup before doing an
upgrade, even on command line.

Franky