New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix chunkator when the primary key is a OneToOneField #19
Comments
zebuline
added a commit
that referenced
this issue
Jun 30, 2017
zebuline
added a commit
that referenced
this issue
Jun 30, 2017
zebuline
added a commit
that referenced
this issue
Jun 30, 2017
zebuline
added a commit
that referenced
this issue
Jun 30, 2017
zebuline
added a commit
that referenced
this issue
Jun 30, 2017
zebuline
added a commit
that referenced
this issue
Jun 30, 2017
zebuline
changed the title
Add the possibility to precise the field used for ordering
Fix chunkator when the primary key is a OneToOneField
Jun 30, 2017
zebuline
added a commit
that referenced
this issue
Jul 3, 2017
closed by #20 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
django-chunkator orders by
pk
.But sometimes, you want to order by an explicit field.
For example:
(with django 1.8 ?) when we write this queryset:
ModelB.objects.order_by('pk')
, it will in background order bymodela__name
.We need to order the queryset by
modela_id
explicitely:Edit: it is possible to fix this case without changing the API. See PR #20
The text was updated successfully, but these errors were encountered: