-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Theo Van Dinter writes: > On Wed, Mar 10, 2004 at 11:23:22AM -0800, Justin Mason wrote: > > How's about a config setting for "support upgrading from v0/v1 dbs", > > defaulting to off? > > Unnecessary since we're not talking about upgrading. :) > > > 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. > > No no no... Upgrading would still work, but using the old DB for check() > and dump and such won't (it currently does) -- our upgrade process is > "upgrade on first write", which is why we recommend people do "sa-learn > --rebuild" after they upgrade (and optionally do the --import if they > have to...) OK, that's perfectly reasonable. +1 on removing v0/v1 support for check() and dump then. PS: if we change again, I suggest we use different filenames? e.g. "bayes_toks3". That would be immediately clear to users that an upgrade is required, that an old db version is in use, and our support for old versions can check once, and quite early, to see if backwards-compat code is required. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFAT4s6QTcbUG5Y7woRArhqAJ9ZwnVDRfEU1A+VJ8nsk9IKnqY+kQCeIyR3 aqvp6bjuUpy0Rfa/VoncaCE= =6PAw -----END PGP SIGNATURE-----
