[Koha-bugs] [Bug 17621] API: Should the 'update_on' Patron field really be a datetime?

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Nov 14 10:04:03 CET 2016


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17621

--- Comment #2 from Martin Renvoize <martin.renvoize at ptfs-europe.com> ---
The simple fact that it's a public facing api makes it different. We handle
timezone internally on the server, but for api consumers if they're not made
aware of the timezone then they cannot do such handling themselves ;)

It's also pretty standard practice to format a datetime to conform to the RFC's
(and swagger allows for this). The RFC's include timezone as part of the
string.

I am aware there's precedent for datetime and date level specificity in
different fields.  I'm just not aware why this field in the Patrons table is
different to the other date fields in the patrons object.  Namely, lastseen,
dateenrolled, dateexpired, debarred.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list