Subject | DDL Versioning |
---|---|
Author | Gerhardus Geldenhuis |
Post date | 2001-10-10T10:01:30Z |
Hi
This is a suggestion/idea. If you find it worth the effort I could have a
dab at it. I would have to learn C first. :-)
Is it not posible to "intercept" all ddl calls and put it in a database or
a set of files. Together with this you would have a versioning system that
keeps track of all changes and who did it. This could help keeping better
track of who did what and helping to make concurrent ddl more stable and
enabling easy rollback.
Maybe rollback is not so practical for all db objects but at least I think
it would work nicely with triggers and procedures. It is highly likely that
I am very much oversimplifying a difficult process so tell me what you
think.
Groete
Gerhardus
This is a suggestion/idea. If you find it worth the effort I could have a
dab at it. I would have to learn C first. :-)
Is it not posible to "intercept" all ddl calls and put it in a database or
a set of files. Together with this you would have a versioning system that
keeps track of all changes and who did it. This could help keeping better
track of who did what and helping to make concurrent ddl more stable and
enabling easy rollback.
Maybe rollback is not so practical for all db objects but at least I think
it would work nicely with triggers and procedures. It is highly likely that
I am very much oversimplifying a difficult process so tell me what you
think.
Groete
Gerhardus