FYI: triggers on system tables (including on rdb$triggers and rdb$procedures)
seem to get dropped the moment I issue a "drop table" command. They stick around
during "create table" though, and will stay active while I create new procedures
and triggers. "drop", however, seems to have some extra side-effects. No idea if
that's intentional or not.

-Philip

---------- Original Message -----------
From: "unordained" <unordained_00@...>
To: firebird-support@yahoogroups.com
Sent: Mon, 16 Feb 2009 00:27:35 -0600
Subject: [firebird-support] Re: triggers on rdb$ system tables, access violation

> I see a message on this list from "Adam" on Sun, 01 Oct 2006 saying that gbak
> won't restore triggers on system tables (as part of a discussion of automating
> the "SERIAL" column type,) but I haven't been doing backup/restores on this
> database. I do have nbackup running regularly though; is there any risk it would
> strip the triggers out somehow? Or in case of server crash, would the startup
> recovery process (inasmuch as one exists at all) strip them out? I did kill the
> server pretty often with bad UDFs, if that explains the disappearing triggers.
>
> -Philip