recentchange doesn't work after loading a db
Posted: Tue Mar 07, 2017 9:24 pm
Running: 1.4.0.713b (x86)
I have 2 instances of Everything running - We'll call them "BG" and "FG".
1. Computer starts up:
c:\> everything -instance BG -db c:\db\mydb.db
c:\> everything -instance FG -db c:\db\mydb.db -readonly
2. Once a day, BG crawls the incredible slow network and indexes the files. It can take many hours to do this (during which time it doesn't handle requests).
3. Once BG finishes crawling, it updates the db file
c:\> everything -instance BG -db c:\db\mydb.db -update
4. FG then exits
c:\> everything -instance FG -quit
5. FG restarts, loading the newly updated database
c:\> everything -instance FG -db c:\db\mydb.db -readonly
6. Goto 2
So this works great in that FG is always available for querying. Is the info out of date sometimes ... yup, but no more than 24 hours and really for what it is used for, that's fine. HOWEVER ...
if after step 5 I run a query such as:
rc:last2days
BG will correctly produce a list of results (maybe 1000 files)
FG will indicate 0 files.
This behavior is consistent. I don't think I'm doing anything wrong:
1. the two instances are sharing the same db
2. I can see that they both report the (correct) same total number of files indexed
This would seem to be a bug where the BG instance has some extra info that it isn't saving to the db that FG is using.
I have 2 instances of Everything running - We'll call them "BG" and "FG".
1. Computer starts up:
c:\> everything -instance BG -db c:\db\mydb.db
c:\> everything -instance FG -db c:\db\mydb.db -readonly
2. Once a day, BG crawls the incredible slow network and indexes the files. It can take many hours to do this (during which time it doesn't handle requests).
3. Once BG finishes crawling, it updates the db file
c:\> everything -instance BG -db c:\db\mydb.db -update
4. FG then exits
c:\> everything -instance FG -quit
5. FG restarts, loading the newly updated database
c:\> everything -instance FG -db c:\db\mydb.db -readonly
6. Goto 2
So this works great in that FG is always available for querying. Is the info out of date sometimes ... yup, but no more than 24 hours and really for what it is used for, that's fine. HOWEVER ...
if after step 5 I run a query such as:
rc:last2days
BG will correctly produce a list of results (maybe 1000 files)
FG will indicate 0 files.
This behavior is consistent. I don't think I'm doing anything wrong:
1. the two instances are sharing the same db
2. I can see that they both report the (correct) same total number of files indexed
This would seem to be a bug where the BG instance has some extra info that it isn't saving to the db that FG is using.