Subject | Re: What can go wrong with indexes after migration from 2.5.1 to 2.5.2 ? |
---|---|
Author | Dmitry Yemanov |
Post date | 2012-12-13T04:45Z |
12.12.2012 14:41, hjcats59 wrote:
Dmitry
>The reason is to ensure that your data is safe and consistent.
> In the Firebird 2.5.2 release notes it is strongly advised to migrate
> databases using gbak backup/restore. or `If this is impracticable, at
> least rebuild all compound indices in the databases being migrated.'
>
> What's the reason for this advise, what can go wrong when indexes are
> not rebuilt?
> Is it because of http://tracker.firebirdsql.org/browse/CORE-3675Yes but not only.
> And if so would it be enough to rebuild indexes with these characteristics:Correct.
> - Compound
> - At least one character column where nulls are allowed
> - UniqueIncorrect.
Dmitry