You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When restoring ODS 11.1 or older databases under Firebird 2.5 or Firebird 3 the RDB$RELATION_TYPE can remain null. This should be fixed up so the value is non-null (either as part of the restore process or somewhere in the engine).
Note that the RDB$RELATION_TYPE is not populated at all for non-system relations; this means that simply changing the value to zero is not sufficient, as that would misidentify views, etc.
To reproduce this, restore a pre ODS 11.2 database.
description: Under unknown conditions (probably restores of old databases), the RDB$RELATION_TYPE can remain null instead of 0 (zero). This should be fixed up so the value is true zero (either as part of the restore process or somewhere in the engine). => When restoring ODS 11.1 or older databases under Firebird 2.5 or Firebird 3 the RDB$RELATION_TYPE can remain null. This should be fixed up so the value is non-null (either as part of the restore process or somewhere in the engine).
Note that the RDB$RELATION_TYPE is not populated at all for non-system relations; this means that simply changing the value to zero is not sufficient, as that would misidentify views, etc.
To reproduce this, restore a pre ODS 11.2 database.
summary: Restore of database can leave RDB$RELATION_TYPE null instead of 0 (zero) => Restore of pre ODS 11.1 database can leave RDB$RELATION_TYPE null
Submitted by: @mrotteveel
Relate to JDBC494
When restoring ODS 11.1 or older databases under Firebird 2.5 or Firebird 3 the RDB$RELATION_TYPE can remain null. This should be fixed up so the value is non-null (either as part of the restore process or somewhere in the engine).
Note that the RDB$RELATION_TYPE is not populated at all for non-system relations; this means that simply changing the value to zero is not sufficient, as that would misidentify views, etc.
To reproduce this, restore a pre ODS 11.2 database.
Commits: 56d787c c04a6ea 2d463a7
The text was updated successfully, but these errors were encountered: