Re: Database schema upgrade in Maia-dev releases

Here is my suggestion:

1) Create an empty mysql schema using the script provided with maia
2) Dump the data from the tables you need
3) Restore your dumped data into mysql

You don't need to dump and restore all the tables but you'll have to 
look through the list of tables and figure out which ones you want to 
keep. Here is the list I came up with that includes all my domains, 
users and configurations (including user's white/black lists) but does 
not include ham, spam or any SpamAssassin data:

     maia maia_config maia_domain_admins maia_domains maia_users 
mailaddr policy users wblist

Because the maia schema includes default values for most of its columns, 
when you insert data into mysql, you don't have to include values for 
every column. This is handy for upgrades.

PJ

On 1/9/16 11:20 PM, Ian R. Justman wrote:
>
> Hi, all.
>
> I hate Mailman's archiving function as there is no reasonably-usable 
> search function.  However, nothing shows in my local archives, so I'll 
> ask here.
>
> It looks like the database schema has been evolving even in recent 
> times. Now, the big question: How hard is it to migrate the databases 
> from an older version of Maia-dev to a newer one? I have data on two 
> servers I'd like to keep if possible. I'm migrating one right now, and 
> while I'd love to get it done this weekend, it's not a priority as it 
> only handles my mail and nobody else's. The other one, on the other 
> hand, is a different matter entirely. I need to have that system 
> working when I finish, preferably with the existing database data, 
> albeit in an ALTERed (MySQL here) state.
>
> Thanks for any help anyone can render!
>
> --Ian.
>

_______________________________________________
Maia-users mailing list
[email protected]
http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users