Milestone dateexpected and release datereleased wrong type in db

Bug #326384 reported by Edwin Grubbs
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The Milestone.dateexpected should be changed into a date column, since the class defines the field as a DateCol.

Currently, the Milestone storm objects set dateexpected to a datetime.datetime object when retrieving a Milestone from the DB, but it sets it to a datetime.date object, when changing the date in code. This causes problems when sorting a list of milestones, since datetime.datetime and datetime.date objects cannot be compared.

Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

ProductRelease.datereleased is also the wrong type. Fixing this requires a migration script.

summary: - Milestone.dateexpected wrong type in db
+ Milestone dateexpected and release datereleased wrong type in db
Curtis Hovey (sinzui)
tags: added: tech-debt
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.