On 7/22/22 04:52, skenny@scss.tcd.ie wrote:
Thanks Mark, that didn't work out I'm afraid. This is what happened when I tried importing without deleting/recreating mailmandb:
I imported the datatase using a psql command in the database container, and then ran "manage.py migrate", which I think does the same thing as the Django admin command with argument "migrate" (?). It reports "No migrations to apply."
In the web interface the lists appear, but without any members, and as before when I the restart the core and web containers, they die after 15 seconds with the error messages as printed below.
(As I mentioned earlier, removing the newly minted mailmandb database and then creating a new blank one, and importing into that does work well (c.f. Stephen Turnbull's remarks above)).
My point was after you remove the newly minted mailmandb database and
then create a new blank one, and import into that, you should then run
manage.py migrate to apply any new migrations to the imported database.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan