Support for transforms in fieldnames #112
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to support transforms in fieldnames (e.g.
datetime__year
), I addedAttributeError
to the caught expections ofio.to_fields
. This changes thetry
block to match what is found in the Django ORM source, which prevents theAttributeError
that would be raised byto_fields
attempting to parseyear
as a related field instead of a transform.Improper transforms or non-existent relations will still raise
django.core.exceptions.FieldError
during thetry_transform
of query processing in the Django ORM.