When I start Imatch - my database - there is a delay of about 40 seconds which seems new - and the log shows
that IM is doing a search during this time. Mario, could you please look at the log to see what is going on.
There is a first delay at the start of 20:05:46 which seems normal.
The strange delay is at the start of 20:06:29
log says:05.08 20:05:47+ 0 [25E8] 10 I> InnerSearchMetabase: Pattern: 'tappeiner', op: 20, groups: 0, tags: 0, scope: 0, lang: '', flags: 1
05.08 20:05:47+ 0 [25E8] 10 M> > 14 CIMQueryManager::InnerSearchMetabase 'IMQueryManager.cpp(1888)'
05.08 20:06:29+42510 [25E8] 10 I> 793 results fetched (vec)
05.08 20:06:29+ 0 [25E8] 10 M> < 14 [42510ms #sl] CIMQueryManager::InnerSearchMetabase
05.08 20:06:29+ 0 [25E8] 10 M> < 13 [42510ms #sl] CIMSearchEngine::RunQuery
05.08 20:06.....
I have done diagnostics, compact and optimize!
The metabase search is triggered by a script. Your script uses CIMSearchEngine::RunQuery to search the metabase.
Please check the scripts you run and make sure they do what you think they do.
IMatch needs 40 seconds to perform the search triggered by your script.
I don't have any event scripts. And this is at startup before I touch any keys.
(But I just found this happens also during normal operation)
Any way to find out what script?
I just starte IM with scripts disabled and the same thing happens!
So it's not a script.
From the log file, I can see that the IMSearchEngine scripting class is used to search for 'tappeiner'.
If you don't run a script explicitly, check the database script, the application script, the App Panel etc.
Thanks.
It was the app panel! The demo search engine app.
Just to learn: what condition triggers such a search? Should it not just be clicking the button?
If there is a search term stored from the last session, the demo app will run the query automatically when the panel is initialized.
Just empty the search term if you don't want this, change the demo app to your liking, switch to another app, e.g. the Copy Data app.