resonate-dev team mailing list archive

[Chris Wagner <christopher.t.wagner@xxxxxxxxx>]

We are simply storing the release dates as a string, at this point,
which seems to work good enough.

** Changed in: resonate
       Status: Confirmed => Fix Committed

** Changed in: resonate
     Assignee: (unassigned) => Chris Wagner (chris-wagner)

-- 
You received this bug notification because you are a member of Resonate
Development Team, which is subscribed to Resonate.
https://bugs.launchpad.net/bugs/555348

Title:
  Come up with a proper fix for storing and displaying release dates

Status in Resonate:
  Fix Committed

Bug description:
  The problem is, not all releases have an explicit year, month, *and*
  day for their "release date". That is, many releases/albums just have
  a year (e.g., 1999), but not a month and day (e.g., 1999-06-07);
  others have only a known year and month.

  Currently, for an album which has no known month and day (or, at least
  not known in the sense that it's not in the track's tag), the release
  date is stored as, for instance, the date "2007-01-01" when it should
  instead be just "2007".

  The trickiest part about this may be coming up with a solution that
  will allow us to sort by the release date, when doing queries to the
  database...  Will a simple string field work?  Maybe a string field in
  combination with a date field?