Hi. Am 04.05.2015 um 23:02 schrieb Ralph Ballier: > > 2_1_7-2_2_0.mysql > 2_3_5-2_3_6.mysql > migrate_from_1.x_to_2.0_innodb.mysql > 2_2-3_0.mysql > 2_3_6-3_0_0.mysql > migrate_from_2.0_to_2.2.mysql > 2_2_5-2_3_0.mysql > 3_0_2-3_1_0.mysql > update_headervalue_01.mysql > 2_3_0-2_3_2.mysql > create_tables.mysql > 2_3_4-2_3_5.mysql > fix_foreign_keys.mysql > > and in sql/mysql/upgrades the files > > 32001.mysql > 32002.mysql > 32003.mysql > 32004.mysql > > Some files, such as 2_1_7-2_2_0.mysql and 2_3_5-2_3_6.mysql is clear > that they do not apply to me. For other files as "create_tables.mysql" > that's not clear. Do I have to eventually run several scripts sequentially? > > In the UPGRADING file is to read: > "Migration of old data is supported through dbmail-util ...". > What does that mean? Do I have to start dbmail-util?
hi. first: the create_tables script only needs to be run for new installs. you need to run the ones relevant for your version. I am not too familiar with the mysql ones (and my upgrade is quite a while ago) but if you ahve 2.2.18 tzhe 2_2-3_0.mysql and then 3_0_2-3_1_0.mysql should be what you need. not sure abou the update_headervalue / fix foreign key ones. the scripts in sql/mysql/upgrades should be applied automatically once you have 3.2. the thing about migrating old data from UPGRADING refers to the migration from the 2.2.x messageblks to mimeparts. from dbmail-util -h output: ... -M migrate legacy 2.2.x messageblks to mimeparts table .. -m limit limit migration to [limit] number of physmessages. Default 10000 ... you need to run that more than once since as you can see it by default only migrates 10k messages at once (since that does take a while and the system is usable before all of those are migrated). Regards, Thomas R
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
