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
Fixed #19434 -- added support for extra_select fields in add_filter #735
Conversation
…icfiles-serve-404 Fixed #20819 -- Return 404 instead of 500 error when ``staticfiles`` vie...
…8498. Thanks CollinAnderson for the report.
All Promise objects were passed to force_text() deep in ORM query code. Not only does this make it difficult or impossible for developers to prevent or alter this behaviour, but it is also wrong for non-text fields. This commit changes `Field.get_prep_value()` from a no-op to one that resolved Promise objects. All subclasses now call super() method first to ensure that they have a real value to work with.
The change also removed allow_explicit_fk from sql/query.py.
Fixed already by previous patch, only test added.
The documentation promises that host validation is disabled when DEBUG=True, that all hostnames are accepted. Domains not compliant with RFC 1034/1035 were however being validated, this validation has now been removed when DEBUG=True. Additionally, when DEBUG=False a more detailed SuspiciousOperation exception message is provided when host validation fails because the hostname is not RFC 1034/1035 compliant.
This PR needs to be reworked so it doesn't include unrelated commits (caused by when someone accidentally force pushed to (django/django)). |
I've updated the patch to work with the current master. But the recent changes to the build_filter method made this patch quite difficult, because it seems like in order to convert the lookup a column and a field is needed. The relevant commit can be found in my fork: fhahn@5c34d6f |
patch for ticket 19434