-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael Parker writes: >On Wed, Mar 10, 2004 at 01:26:05PM -0500, Theo Van Dinter wrote: >> On Wed, Mar 10, 2004 at 02:22:51AM -0800, Dan Quinlan wrote: >> > 1. It seems like we spend a fair bit time figuring out whether tokens >> > are magic tokens: >> > >> > %Time ExclSec CumulS #Calls sec/call Csec/c Name >> > 1.80 0.310 0.458 47786 0.0000 0.0000 >> > ::BayesStoreDBM::is_magic_token >> > 1.28 0.220 0.196 47786 0.0000 0.0000 ::BayesStoreDBM::get_magic_re >> >> This is very likely due to backward compatibility (ie: we read v0 and v1 >> DBs). >> > >Ok, I'll ask. Anyone for removing backward compatibility for v0/v1 DBs? How's about a config setting for "support upgrading from v0/v1 dbs", defaulting to off? What I'd hate is to have to say to someone: "you need to install SpamAssassin 2.63, run a command, then install SpamAssassin 3.0.0 over that and run another command". I've run into products that do that, before, and it's a world of pain for users. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFAT2sqQTcbUG5Y7woRAkWmAKDmiVWZ4EYEJZRQ+tOKPLruUDb8ggCeKlCP ny1JSIeCajSfC1qYfHrUzZk= =OEry -----END PGP SIGNATURE-----
