> I think a better approach is to handle configuration management with a
> table in each schema. Update the schema, update the table. This works
> well with automating database upgrades as well, where upgrades are written
> as scripts, and applied in a given order to upgrade a database from release
> A to C, or A to X, depending on when it was archived. A script naming
> convention (e.g. numerical) can determine order, and each script can
> register in (write a line to) the configuration management table. This
> allows for error analysis, among other things.
>
> Rick
I'm currently looking at implementing a system almost exactly like this,
and I was wondering if there is anything around that does this.
Jeff
