Fix up a couple places that used select_related() with incorrect field names.
Review Request #8697 — Created Jan. 31, 2017 and submitted — Latest diff uploaded
Django 1.8 helpfully throws an error if
select_related()is called with a
field name that doesn't exist. There were a couple places that were doing this
(columns in the reviews datagrid on the users page and the e-mail
notifications), and we just didn't notice that they were doing more queries
than expected as a result.
Ran unit tests.