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
on-nullable field 'order' to mapping without a default #140
Comments
Could you explain in more detail what this is about? |
self.swap(self.get_ordering_queryset() if all order fields is 0, qs is blank, and all methods up and down not work |
Yes it's a known issue that your models need to be ordered from the start. If you retrospectively add ordering using |
Is this any closer to being resolved? |
Yes - the admin tool to re-order an existing model is now merged #188 and released in version 3.4.2 |
No description provided.
The text was updated successfully, but these errors were encountered: