#24596: year_lookup_bounds_for_date_field should be evaluated via
get_db_prep_value
in get_db_prep_lookup
----------------------------------------------+--------------------
Reporter: nutztherookie | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
I think the summary says it all..
If i return `datetime.date` or `datetime.datetime` objects from my
overwritten `year_lookup_bounds_for_date_field()` function they will not
be casted to a corresponding string for the database to understand.
i might be making a mistake some place else in my database driver, but my
solution right now is attached here as a patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/24596>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.372366614f139f4bad466c21e680f644%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
