FK origin + destination fields should have "unique together" DB constraint about metabase HOT 3 CLOSED

These two cols should have a (forgive my Django-tard terminology) unique_together DB constraint.

I think our code has improved to the point that we aren't creating these duplicates anymore. Are we still seeing this issue? Depending on the number of people with this issue we'll probably want to write a migration that deletes duplicate instances first before adding the constraint

from metabase.

I think we can safely skip writing a migration for this. We fixed this a while ago and there is no reason to believe anyone is running into this issue at this point because all the known running instances are on fairly recent builds.

I think we can just close this.

from metabase.

👍

On Wednesday, October 7, 2015, Allen Gilliland [email protected]
wrote:

I think we can safely skip writing a migration for this. We fixed this a
while ago and there is no reason to believe anyone is running into this
issue at this point because all the known running instances are on fairly
recent builds.

I think we can just close this.

—
Reply to this email directly or view it on GitHub
#586 (comment).

from metabase.