Re: Speeding up the upgrade process from 2.2 to 3.1
Casper Langemeijer <[email protected]>
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Message-ID | <[email protected]> |
On 15-09-14 13:55, Reindl Harald wrote: > Am 15.09.2014 um 13:40 schrieb Casper Langemeijer: >> I noticed dbmail_messageblks data is never written into the dbmail_mimeparts, >> table. My guess is that the current dbmail code can still handle dbmail_messageblks, >> and conversion is not required > that change is sooner or later needed because 3.x uses single > instance storage (de-duplication) and likely that code will > not be maintained and well tested forever > > doing that migration in a few years hence is more dangerous > I understand dbmail-util -M needs to be ran at some point, but that is not a problem. My problem is the primary key changes, from signed to unsigned bigint's. I understand that it doesn't make sense to have a signed id column, but it makes even less sense to correct that 'problem' during migration and cause downtime doing it. I'd rather keep my signed columns. I created my own 2_2-3_0.mysql file. Currently it's untested, but I diff'ed the result with the database structure created with create_tables.mysql and I see no problems. If anyone else is interested, you can find the sql script here: https://gist.github.com/langemeijer/23251898ab22265ed7e7 Greetings, Casper