Model validation requires that ForeignKey be unique (backwards-incompatible change)
|Reported by:||jbalogh||Owned by:||nobody|
|Cc:||davedash, clouserw, wenzel||Triage Stage:||Unreviewed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Much to my chagrin, our MySQL app relies on this. I know it's wrong, but it's what I have to work with right now. The table I'm using has a uniqueness constraint on a pair of fields, not just the ForeignKey. I override the pieces that expect uniqueness, but for the most part the ForeignKey machinery just works.
We were fine until validation got more strict.