The original equipment->device rename migration's ALTER INDEX RENAME was a no-op (the index didn't exist by the legacy name at that point in the migration sequence on existing databases), leaving the unique index named agent_assignments_equipment_id_index. The schema's unique_constraint now expects agent_assignments_device_id_index, causing a constraint violation to surface as Ecto.ConstraintError instead of a changeset error. |
||
|---|---|---|
| .. | ||
| migrations | ||
| seeds.exs | ||
| seeds_e2e.exs | ||
| structure.sql | ||