Page 1 of 1
Searchable Cache Database [Enhancement]
Posted: Fri Nov 21, 2003 11:03 am
by Evds
Hi,
It would be great if it would be possible to search for pictures with a certain name (wildcards) which are stored in the cache database.
At that point it would also be useful if the pictures you have looked at on a removable media (cd) are also cached in the database.
Ps: superb program
Posted: Mon Nov 24, 2003 6:46 am
by crazytb
Good idea! I don't use cache here (but I like to use), and I don't know how the filenames are stored at cache. You may try to search directly on cache file.
But I think this is a good feature and should be implemented.
Re: Searchable Cache Database [Enhancement]
Posted: Mon Dec 22, 2003 9:07 pm
by helmut
Evds wrote:It would be great if it would be possible to search for pictures with a certain name (wildcards) which are stored in the cache database.
The cache exists for technical reasons (performance). I can't see the advantage/purpose of searching the cache.
Re: Searchable Cache Database [Enhancement]
Posted: Tue Dec 23, 2003 5:08 am
by crazytb
helmut wrote:Evds wrote:It would be great if it would be possible to search for pictures with a certain name (wildcards) which are stored in the cache database.
The cache exists for technical reasons (performance). I can't see the advantage/purpose of searching the cache.
Seaching in cache will be for technical reasons (performance).
The idea is:
1. I put a clipart CD on my drive.
2. I browse it, and generate cliparts for it.
3. I may browse other folders (in HD) as well.
4. I put another CD (but before remove the first CD
).
5. I repeat the step 2.
Days after, I want to see if I had some "yellow smile" picture. So, looking directly into cache will be fast and will avoid the work of changing CDs. And also, browsing directly into cache, I will be able to see the path of image before opening the image itself.
The idea of "find in cache" is similiar to Linux "locate" utility. This one has a database with a list of all files of current filesystem. Then, locating is much faster, because it just looks at its database (which is some megabytes?), instead of entire disk (which is some gigabytes!).