__year search trouble on 1st of january
|Reported by:||Dirk Datzert <dummy@…>||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||master|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||yes||Patch needs improvement:||yes|
I detected in a data_hierarchy filter a strange behavior of dates at 1.1. of a year. I have a field birthday defined as a models.DateField(...). I'm working with a sqlite3 database, python2.5 and django-trunk.
Selecting in the admin view the year say 1990 all dates above 1.1.1990 are selected but not the 1.1.1990 himself.
Maybe this was introduced by the  patch!?
Change History (15)
Changed 9 years ago by Dirk Datzert <dummy@…>
comment:1 Changed 9 years ago by Dirk Datzert <dummy@…>
- Has patch set
- Needs documentation unset
- Needs tests set
- Patch needs improvement unset
comment:2 follow-up: ↓ 4 Changed 9 years ago by mtredinnick
- Patch needs improvement set
- Triage Stage changed from Unreviewed to Accepted
comment:4 in reply to: ↑ 2 Changed 9 years ago by Nebojsa Djordjevic <nesh@…>
- Component changed from Admin interface to Database wrapper