I'm using 1.11 and have a migration that is throwing:
"inventory_ltmvirtualserver_ltm_id_47dc1635_fk" for relation
"inventory_ltmvirtualserver" already exists
I'm having troubles figuring this out for a couple reasons. First, the
migration scripts ran fine against the development and stage environments
and only fails in production. Also, if I export the production database
and import that copy to the development environment the migration works
The other issue I'm having is that the migration in question
(inventory.0040_auto_20180104_1225) doesn't actually reference the
"ltmvirtualserver" model. I can't figure out why the migration is
attempting to create this constraint.
The backend database is Postgres.
What information can I provide to help track this down? Migration
scripts? Is there a way to get the precise line in the migration script
that is being processed when the error is thrown?
Thanks in advance for the help.
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.