On 03/17/2018 01:44 PM, Bjoern Franke wrote:
is it possible to migrate a mailman3-mysql-database to a postgresql-database?
I tried to convert it with pgloader, but some identifiers had to be cut off: _address_id); 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac gekrzt
I suspect the issue is due to the way Mailman supports different databases via SQLAlchemy. The bottom line is the table and column specifications are based on the Mailman database models, but are database specific.
If I were doing this, I would dump the data from MySQL, but rather than using the CREATE TABLE queries from the dump, I would let Mailman create a new PostgreSQL database and then just load the existing tables from the MySQL dump.
However, that may all be irrelevant. I don't know which table/column that specific item comes from, but it appears just visually that
is already truncated so further truncating it to
may not be a problem.
-- Mark Sapiro firstname.lastname@example.org The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan