Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#8931 closed (invalid)

Queries on datetimefields return incorrect results in mysql

Reported by: ElliottM Owned by: nobody
Component: Database layer (models, ORM) Version: 1.0
Severity: Keywords: datetime mysql query
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


In my models, I have a Planet class. One of the fields in Planet is a datetime field called updated. I also have a class called Base that has an o2o to Planet. The Base class also has an FK called "owner"to the Player class.

When I want to find all the bases whose planets were updated in the last six weeks, I should be able to do the following:*6)

That query returns no results. However, if I further refine the query to get only the bases owned by a particular player, like follows:


That query returns 18 results, as expected. It think it's pretty obvious that narrowing down the search criteria should reduce the number of results, not increase them, and I know there are Bases that have been updated in the last 6 weeks.

Change History (2)

comment:1 Changed 14 years ago by ElliottM

Resolution: invalid
Status: newclosed

Turns out this was a problem with mysql and not with django.

comment:2 in reply to:  1 Changed 14 years ago by Karen Tracey

Replying to ElliottM:

Turns out this was a problem with mysql and not with django.

Some details of the mysql problem could be helpful for when the next person to hit this searches the tracker, finds this report, and re-opens this as a bug in Django. Is is a mysql bug logged in their bug system? A configuration problem?

Note: See TracTickets for help on using tickets.
Back to Top