We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems like somebody forgot ordering = ['pk'] in Meta
ordering = ['pk']
Meta
oioioi/oioioi/problems/models.py
Lines 818 to 838 in 5414a6c
DifficultyTagLocalization
oioioi/oioioi/problems/views.py
Line 556 in 5414a6c
.order_by()
perhaps the ordering should be more explicit in the first place rather than relying on the autogenerated pk field?
pk
The text was updated successfully, but these errors were encountered:
As a bonus: Seems like the styling on these buttons is a bit broken, not to mention the inconsistent heights.
Sorry, something went wrong.
reivvax
Successfully merging a pull request may close this issue.
Seems like somebody forgot
ordering = ['pk']
inMeta
oioioi/oioioi/problems/models.py
Lines 818 to 838 in 5414a6c
same goes for
DifficultyTagLocalization
, which is why this code returns unsorted rows (per SQL specs rows are not automatically sorted by any field)oioioi/oioioi/problems/views.py
Line 556 in 5414a6c
so another fix would probably be adding an
.order_by()
here?perhaps the ordering should be more explicit in the first place rather than relying on the autogenerated
pk
field?The text was updated successfully, but these errors were encountered: