Subject Re: DDL Versioning
Author Thomas Steinmaurer

I thought about that some months ago, when starting the
implementation of IBLogManager v2.x. I had SERIOUS problems (not
solved yet) to make user-defined triggers on system tables reliable.
Well, they can be defined, but something strange was
going on. After reconnecting they don't fire anymore and they must be
recompiled to keep them active, ...
This was with IB 6.01. Don't know about Firebird, haven't tried it

Thomas Steinmaurer

--- In IBDI@y..., Paul Reeves <paul@f...> wrote:
> Gerhardus Geldenhuis wrote:
> >
> > 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.
> I've never looked seriously into this, but it should be feasible to
> this by judicious use of triggers on system tables.
> Paul
> --
> Paul Reeves
> taking InterBase further