There you have it: upgrade to 2.0, add new tables for 2.1. 2.1's db-schema is forward compatible with 2.0: you can add the new tables for 2.1, try 2.1, go back to 2.0. The new tables are then simply not used after moving back to 2.0.
Leonel Nunez wrote: > Paul J Stevens wrote: > >> Dbmail-2.1.1 was released today. It marks a major milestone on the path >> to a 2.2 release. >> >> You can download this package from: >> >> http://www.dbmail.org/download/2.1/dbmail-2.1.1.tar.gz >> >> Some of the main highlights include: >> >> * make dbmail servers in prefork mode die when the database backend >> dies, and recover when the backend is restarted (closes #190). >> * finished the headercaching code to include support for from, to, >> cc, (base)subject, (sent)date, references, and in-reply-to >> headers. >> * plugged lots of memory leakage and a couple of a double frees. >> * added Jesse Norell’s usermap feature. >> * expanded the usermap to support ip-based virtual-hosting. >> * fixed auto-reply. No more loops or mail-storms. >> >> >> > > > Will there be a clean path to upgrade from 1.2 to 2.2 ? > or do I have to move to 2.0 and then to 2.2 ? > > > Leonel > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
