Locality Integrity Error: django.db.utils.IntegrityError: (1062, "Duplicate entry... about django-address HOT 3 CLOSED

Adding my own comment here since the owner doesn't appear excited to answer. I find it's best to just drop that constraint altogether. You'll have plenty of instances in which the postal_code will differ but the state_code and name in the address_locality table will remain the same. You can fix this with the following steps:

SHOW CREATE TABLE address_locality;

find the index that binds "name" and "state_id", and drop the constraint with that name. In my case, address_locality_name_5eb72081b80e9d3d_uniq.

ALTER TABLE address_locality DROP INDEX address_locality_name_5eb72081b80e9d3d_uniq

from django-address.

A little more on this - While the steps above go so far as to remove the database constraint, there is still a built-in constraint living in the model declaration of the app. To remove this, you'll need to open up the models.py file in the app and comment out/delete the line from within the Locality(models.model) declaration that enforces this constraint. On my file, it's line 199: unique_together = ('name', 'state'). Hope this helps!

from django-address.

Thank you @keubs for this report. This was resolved as described in #63. Please see #98 for updates on django-address.

from django-address.