Prevent saving overlapping time periods in user history data

[jaragunde]

[Trac import] Reported by: jaragunde Original date: Monday, 19 September 2011 13:54

Users have four tables tracking history of their hour cost, journey, area and city. Right now overlapping time periods are allowed but that's incorrect, and it can cause problems in other parts of the application that assume these data are always correct (see #153).

A check to prevent these incorrect data being saved should be placed both at model layer and user interface levels, with priority to the lowest one.

[jaragunde]

[Trac import] Comment by: jaragunde Original date: Tuesday, 15 January 2013 11:18

Issues caused by this bug arise from time to time, and they are difficult to detect.