On 7/21/22 08:09, skenny@scss.tcd.ie wrote:
I was afraid that by removing the default database that comes with the database container, I'd be losing some vital information that may have been added or changed in the database config since I first got my production server working 2 years ago - changed field values, extra table columns ... ? Does that make any sense? I've a hazy understanding at best of the minutiae of databases, being honest.
You should run your Django admin command with the migrate argument,
however you run that in your container after you import the database to
apply any necessary migrations. This should fix any issues with added
columns or changed definitions.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan