Jim Starkey wrote:

> I would like to see a careful, thoughtful design, something that would
> allow any backup that ran to completion to be restored. This will
> certainly require the ability to disable various constraints when
> necessary. It certainly would require the ability to disable foreign
> key checking on specific foreign keys (a very good thing in its own
> right).

Broken foreign keys problem is solved in fb2. There has always been
code, that tried to leave index of broken foreign key in INACTIVE state.
But (probably due to borland's changes in system triggers) that code
didn't work properly. Now it's fixed, and GBAK leaves index INACTIVE,
prints appropriate message and leaves database shutted down (not more
then single SYSDBA attachment) after restore completion.