Opened 17 years ago

Closed 17 years ago

#5391 closed (duplicate)

date_hierarchy breaks for date objects of January 1st

Reported by: Nathaniel Whiteinge <whiteinge@…> Owned by: nobody
Component: contrib.admin Version: dev
Severity: Keywords: date_hierarchy qs-rf
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Verified with the following test model. Add a few entries of January 1st for differing years. DateTimeField fields do not have this problem. Appears to affect at least SQLite and MySQL.

class Test(models.Model):
    test = models.DateField()

    class Admin:
        date_hierarchy = 'test'

    def __unicode__(self):
        return str(self.test)

Change History (3)

comment:1 by flother, 17 years ago

This sounds like it's related to #5365 and #391.

comment:2 by flother, 17 years ago

Keywords: qs-rf added

comment:3 by James Bennett, 17 years ago

Resolution: → duplicate
Status: new → closed

This feels like another variation of #3689 and #5365.

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