On 7 Oct 2004 at 14:02, Ann W. Harrison wrote:

>Relation and field ids are designed to be specific only to
>an instance of a database. Back it up and restore it and you
>get another set of ids. That's a good thing. You'll find
>that the BLR for procedure uses relation and field names.
>System objects that are recreated (e.g. RDB$FORMATS and
>RDB$PAGES) use ids.

That's sad. And it became even more sad because system tables don't
have PKs. It means that I can't prevent user from dropping table that
my application depends on. Can't create FK to system table. Not sure
about triggers... If I create triggers for system table will they
survive during backup/restore?
IBReplicator is an example of application that suffer from this
"feature". It'll crash if someone drop table for which there are
pending operation in log.

SY, Dimitry Sibiryakov.