Timestamp on dob can make date appear off by a day
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
Bug Description
A discrepancy on timezone between client and server can make a birthdate created as '2011-01-01 00:00:00-4' end up as '2010-12-31 23:00:00-5' server side. This can make the dob appear as 2010-12-31 or 2011-01-01 depending on where it's viewed.
As a temporary work around, I'm adding 1 hour in register.js, to allow for the difference. This makes some dob's appear with a time of 01:00:00-05, but at least its on the same day, and at a time that's rarely an issue for patron interactions.
I can't think of an argument for the the dob not being a "date" type, instead of "timestamp with timezone".
I've identified the following functions and views that would need to be dropped/created to facilitate this change, and have done very minor testing, with no ill effects.
FUNCTION auditor.
VIEW reporter.
VIEW action.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | 2.next → 2.10-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
> As a temporary work around, I'm adding 1 hour in register.js, to allow
> for the difference. This makes some dob's appear with a time of
> 01:00:00-05, but at least its on the same day, and at a time that's
> rarely an issue for patron interactions.
I have vague recollection of adding 8 or 12 hours; maybe in the original editor?
-- Jason