Actually, I’m very new in the world of tabbles, and I don’t use the software much (only 2 days at work, but had too little time to gain real experience). I breafly looked through the forum (god bless, it is small 😀 ) and had some ideas which I posted here.
After thinking next 5 minutes I’ve understood why hashing and indexing would blow the performance completely – just imagine, what time you need to generate the hash number for only one large sized file?.. Even worse – you need it to do with all the files from the storage when you will do reindex (relinking). So the idea is good only when the file has it’s hashsum at the OS/FS level, which is not implemented in windows FS, as far as I know.
One way to manage auto relinking – find the files by their unique properties – name, size, may be date and time of creation (I don’t know, whether it changing everytime or not… well, checked – all the dates are changing everytime 🙁 ), assuming that all the files are different, which in general is not an issue… Anyway, it will inflate DB again.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.