Closed firebird-automations closed 16 years ago
Commented by: @pcisar
Well, this is not a bug. If anything, it's deficiency in Release Notes, but that's all. FB 2.0/2.1 has different ODS than 1.5 line, so it's no surprise that system generated index names doesn't match. If you want to specify explicit PLANs in SP's, you should use named constraints, so index names will be ODS independent.
Commented by: @asfernandes
We definetivelly should investigate this bug report.
Index names are backup-ed and restored no matter if the name is system generated.
Also, the engine doesn't have primary keys, so ODS change can't introduce extra RDB$PRIMARYn indexes names.
Commented by: @pcisar
Ok Adriano, reopened.
Commented by: @asfernandes
Leonid, can you attach a metadata backup?
Commented by: Leonid (leonbn)
It is the very simplified variant
Commented by: @asfernandes
I could not reproduce any problem!
Commented by: Leonid (leonbn)
I'm sorry. All problems because of the incorrect plan. The core can be closed.
Commented by: @hvlad
Reporter was mistaken ;)
Submitted by: Leonid (leonbn)
Attachments: example.fbk
Has primary key PK_TOVARS on table TOVARS with index name RDB$PRIMARY4. And has stored procedure with PLAN in select, for example, PLAN JOIN (LINKST INDEX (LINKST_IDX1),TOVARS INDEX (RDB$PRIMARY4)). Backup/Restore on version 1.5.x is pass OK . When i do restore this database on version 2.1 it fails with message "Invalid token. invalid request BLR at offset 3154. there is no index RDB$PRIMARY4 for table TOVARS."