Using Index IDs for Lower Memory Usage
Using Index IDs for Lower Memory Usage
Hello, can the Everything SDK return index IDs directly when returning results, and then query column content through these index IDs? This way, the memory usage should be lower when calling the SDK for searches, and it could also enable more extended functionality.
Re: Using Index IDs for Lower Memory Usage
Everything doesn't have index IDs.
Everything uniquely identifies a file/folder by index number and filename.
I have on my TODO list to add an API to get the property values for a single file/folder.
There are API functions to get basic file information from a filename.
For now, for other properties, you'll need to execute a search and request the desired properties.
Even if it is for just one file/folder.
For example:
Everything uniquely identifies a file/folder by index number and filename.
I have on my TODO list to add an API to get the property values for a single file/folder.
There are API functions to get basic file information from a filename.
For now, for other properties, you'll need to execute a search and request the desired properties.
Even if it is for just one file/folder.
For example:
wholefilename:"C:\Program Files\Everything\Everything.exe"