Michael Monnerie wrote:
If it's for the full length line, it could be good for searching double values on INSERT time. But only for that, or is there any other use?
No, not at the moment.
The question is: Is it worth the effort? If the hash is reasonably short, I guess yes. It should be limited to 16 bytes (to save disk space) and allow duplicates, because it doesn't matter to have a hash crash here when you compare the full text afterwards. You can easily SELECT ... WHERE hashfield='computed_hash' AND headervalue='new_line' and the db can use the index over hashfield to find only the 1-2 hashes that fit and finally compare contents using the full line.
good idea. Currently we're doing the value comparison in dbmail, but leaving it to the database makes perfect sense.
BTW: Do you allow hash crashes in the single instance store of the messageparts? I guess yes.
Yes, hash collisions are allowed. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
