I don’t dislike the idea in general, but in my case I really wouldn’t want to create a through model to keep the complexity down: in my application, I really just use selected_choice as an array, conceptually; also, I would have to mess with the way my serializers assign to the field.
I believe there has to be a way to perform validation on the field: for example, if you supply the PK of a model that doesn’t exist at all, Django is able to catch and report a ValidationError, so some additional code might be inserted at that spot, if I can identify it.
Agreed. My whole application is an LMS so most of the data models stuff that is questionnaire-related, and some things have been pretty hard to design.