Launchpad itself

Fix bad milestone date that causes oopses

Asked by Curtis Hovey

OOPS-1696K1492 was caused by a user who entered 1010 for the year the milestone was expected. The date has to be after 1900. The code is fixed on edge, but users can still shoot themselves in the foot on lpnet. This happened a few weeks ago and we discovered we could only fix it using SQL.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Solved by:
Curtis Hovey
Solved:
Last query:
Last reply:
Whiteboard:
update milestone set dateexpected = dateexpected + interval '1000 year' where dateexpected < '1011-01-01';
Revision history for this message
Curtis Hovey (sinzui) said : 		#1

Stephan fixed the data issue