Subject | RE: [ib-support] Triggers |
---|---|
Author | Helen Borrie |
Post date | 2002-03-12T05:20:33Z |
At 07:39 PM 11-03-02 -0800, Tony wrote:
Ann fixed up Firebird so that this does not increment the change count on
the table it belongs to:
ALTER TRIGGER my_trigger INACTIVE | ACTIVE
Borland copied Ann's changes to IB 6.5. Lower IB versions still have the
problem.
It still remains that any ALTER TABLE will increment its change count by 1,
up to the max. 255. AFAIK, DROP TRIGGER and CREATE TRIGGER...FOR will
still affect the change count (Ann or Claudio will set us right if that is
incorrect). The purpose of the change count limit is to ensure that
databases under intensive (re)development get properly cleaned up at
appropriate intervals. A database can't run gbak on itself so, if
anything, it's a way of kicking a sloppy programmer's butt.
cheers,
Helen
>Are saying that Firebird does not suffer from the 255 instances issues withLet's be clear.
>ALTERING tables. If so, does Firebird have an instance limit?
Ann fixed up Firebird so that this does not increment the change count on
the table it belongs to:
ALTER TRIGGER my_trigger INACTIVE | ACTIVE
Borland copied Ann's changes to IB 6.5. Lower IB versions still have the
problem.
It still remains that any ALTER TABLE will increment its change count by 1,
up to the max. 255. AFAIK, DROP TRIGGER and CREATE TRIGGER...FOR will
still affect the change count (Ann or Claudio will set us right if that is
incorrect). The purpose of the change count limit is to ensure that
databases under intensive (re)development get properly cleaned up at
appropriate intervals. A database can't run gbak on itself so, if
anything, it's a way of kicking a sloppy programmer's butt.
cheers,
Helen