Re: [WWdevel] some 2.3 notes for you all

[Michael G. <ga...@ma...>]

Hi Sam,

I think this feature should be the highest priority for your time.
A beginning stub for database update will be useful -- it may not
be full featured, but that's ok as long as the stub is moving in the  
right direction.
On Aug 3, 2006, at 2:05 PM, Sam Hathaway wrote:

> -- Automatic Database Update --
>
> wwdb_check will do simple things like adding tables/columns/indexes,
> changing
> column types, and the like. this is sufficient for gavin's current
> changes.
>
> eventually, we need a real database versioning system for more
> complicated
> changes -- filling default values, normalization, and the like -- but
> we don't
> technically have to have this mechanism in place right now.
>
> we just need to ensure that the state of 2.3.0 databases is:
> 	- all tables/columns/indexes up-to-date and using the correct types
> 	- dbupgrade table exists
> 	- db_version=0 in dbupgrade table
>
> (i'm also starting to think that the database upgrading should
> happend offline,
> in a command-line script.)
This is ok with with me, but I'd like it to be something that is checked
when the server starts up or restarts (there is an Apache hook for  
that which might
be the right thing to use.)  We do something like this for checking  
global.conf
and for that matter it wouldn't hurt to run a version of the  
check_modules script.
I really like the behavior of moodle which is quite good about  
insuring database
updates when ever an update of the system takes place, but we might
not be able to achieve that all in one go.

Take care,

Mike