#2's not a bug, m2o search widgets have always had CharField semantics, the =id in case of exact match is a usability optimization for the default domain, in case the user specifically chose something from the autocompletion list. Putting the m2o id instead is going to break existing code.
For exact ids, the m2o field needs to use a selection widget.
#2's not a bug, m2o search widgets have always had CharField semantics, the =id in case of exact match is a usability optimization for the default domain, in case the user specifically chose something from the autocompletion list. Putting the m2o id instead is going to break existing code.
For exact ids, the m2o field needs to use a selection widget.