[mir-coders] tracking updates to the db

[pietro]

new version of the patch, now i also add a model_version table to the db.

pietro.

On Thu, September 1, 2005 4:41 pm, pietro wrote:
> hi folks,
>
> i was thinking about a way to keep track of which updates were applied to
> a db to make admins lives easier and also to make it possible for a script
> to update a mir installation withou having to run all the db update
> scripts when just a few or none are needed.
>
> i came up with the idea of using a table to keep track of which updates
> were applied to a db. it has an id, a date and a description of the
> update.
>
> i'm attaching a diff to the create_pg.sql and createmirdb.sh scripts to
> get the table created in a new install. the populate_dbpatches.sql is to
> get the a new db with the data of the patches written so far and the
> update20050901.sql is an update that existing sites should run.
>
> i appreciate any comments, ideas and criticism. please remember that i'm
> not an expert in databases and nor postgres.
>
> pietro.
> _______________________________________________
> mir-coders mailing list
> mir-coders at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/mir-coders
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: update20050912.sql
Type: application/octet-stream
Size: 2170 bytes
Desc: not available
Url : http://lists.indymedia.org/pipermail/mir-coders/attachments/20050912/5ab4dbcd/update20050912.obj