- Feb 23, 2019
-
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
- Feb 22, 2019
-
-
Jean-Sébastien Caux authored
-
- Feb 21, 2019
-
-
Jean-Sébastien Caux authored
-
- Feb 20, 2019
-
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
- Feb 19, 2019
-
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
- Jan 08, 2019
-
-
Jean-Sébastien Caux authored
-
- Nov 12, 2018
-
-
Jean-Sébastien Caux authored
-
- Oct 12, 2018
-
-
Jean-Sébastien Caux authored
-
- Oct 10, 2018
-
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
- Oct 08, 2018
-
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
- Oct 07, 2018
-
-
Jorran de Wit authored
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-
- Oct 03, 2018
-
-
Jean-Sébastien Caux authored
-
- Oct 02, 2018
-
-
Jean-Sébastien Caux authored
The solution involves a bit of hacking via a list comprehension of ids, since related_name='+' has been set for contributor and unregistered_author fields of PublicationAuthorsTable. The previous version returned the wrong sort of objects, i.e. return self.publicationauthorstable_set.select_related( 'contributor').order_by('contributor__user__last_name') returned PublicationAuthorsTable objects instead of Contributors
-
- Sep 22, 2018
-
-
Jean-Sébastien Caux authored
-
Jean-Sébastien Caux authored
-