-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Montag, 13. Dezember 2004 16:04 schrieb Michael Parker: > On Sun, Dec 12, 2004 at 11:21:19PM -0800, Gary W. Smith wrote: [..] > As of 3.0 the bayes tokens are stored as a part of an SHA1 hash on the > original token string. So, there is no way to extract that data from > the database. There was a very long discussion on this and several > queries to the mailing list to determine if anyone was using that > functionality in a meaningful way. The fact is, storing the tokens as > a fixed length SHA1 hash speeds up processing speed by a large factor > so it was a true win. An effort was made to give the option of > storing the raw token value but it lead to unacceptable slowdowns even > when turned off. > > That said, a compromise was put into the code that could help you in > your situation. A few plugin hooks where added at various points in > the bayes code so you could extract the raw token values and map them > to their binary counterparts. With a plugin you could pretty easily > start gathering data (especially on commonly used tokens) and use that > data to map the binary to the raw token value for your scripts. >
Where can we find a documentatioon about this. The man page is not updated and the --regexp option is now useless but not marked as deprecated. Thomas - -- icq:133073900 aim:tawhv -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.3.92 (GNU/Linux) iD8DBQFBvf23He2ZLU3NgHsRAkUIAJ9MRNxlLyQdPutKQk85XSIY0h1McQCcDbi8 IKfkKhtNlgAmGE6YSJqkRE0= =xoee -----END PGP SIGNATURE-----
