Have a look at
http://git.dbmail.eu/?p=paul/dbmail;a=tree;f=sql;h=db840570d289ebbe1d77101724ec35a37ae03cf7;hb=master
From there click on your database platform, then click on history next
to the create_tables file.
2.3.2 came out on 2008-02-09, so any commits past date you should click
on the commitdiff to see what tables are touched.
The latest commit "misc fixes" is only for code that is after the
tarball - so don't do that change.
For mysql is looks like the dbmail_mimeparts.hash column was changed
from char(64) to char(128). That is the only change to the schema for
that platform.
Simply do a:
ALTER TABLE dbmail_mimeparts MODIFY COLUMN `hash` char(128) NOT NULL;
That should be safe to do.
Don't drop this table as all of your mail is in it.
a mysqldump of the database would be a good idea before fooling with it
though, just in case.
-Jon
dan wrote:
On Fri, 14 Nov 2008 14:48:01 +0100, Paul J Stevens <[EMAIL PROTECTED]> wrote:
Hi all,
It is with great pleasure that I'm announcing the availability of DBMail
version 2.3.4, the latest in the 'unstable' development series.
Cool. Will update soon. Any caveats moving ( home server ... no I'm not
using in production ) from 2.3.2 to 2.3.4 ... ie are there any rolling
changes I need to apply to the DB from 2.3.3?
Dan
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
