2 | | Correcting myself - some of the unexpected behaviors described above result from logic in BaseModelFormSet._construct_form and are not addressed by the concept I proposed. As I investigated, scope broadened and that logic IS logically part of validating the pk value, but is needed to associate the form with its instance. Still thinking... |
| 2 | Correcting myself - some of the unexpected behaviors described above result from logic in `BaseModelFormSet._construct_form` and has little to do with this issue. As I investigated, scope broadened and that logic IS logically part of validating the pk value, but is needed to associate the form with its instance. Still thinking... |
| 3 | The code I proposed at least raises a validation error in cases (a) and (b). Case (c) seems most critical, but can't be detected at form level - it's a formset validation issue. |