1402 & -read-only, potentially always Migrating...

Discussion related to "Everything" 1.5.
Post Reply
therube
Posts: 5723
Joined: Thu Sep 03, 2009 6:48 pm

1402 & -read-only, potentially always Migrating...

Post by therube »

1402 & -read-only, potentially always Migrating...

If you have an existing ESDb1 that you open -read-only,
& you open it in Everything > 1400
you will always have a Migrating... condition.

So if all you did was to update Everything.exe
from 1400 to 1402
& then you open said -read-only instance
all opens will open, Migrating...

Is there a way around that (other then allowing update or copying in an updated ESDb2 .db)?
void
Developer
Posts: 19870
Joined: Fri Oct 16, 2009 11:31 pm

Re: 1402 & -read-only, potentially always Migrating...

Post by void »

Unfortunately, there's no way around it, 1401+ uses a different database structure.
(different indexed property structure, different journal database, different sorting and different string comparison)

I recommend
Using 1400a with your older dbs.
-or-
Waiting for 1402 to mature a little, then update your db.
Post Reply