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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Jan 9 07:59:17 CET 2017


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

--- Comment #5 from Martin Renvoize <martin.renvoize at ptfs-europe.com> ---
OK, I think my point here was more about the api returnter_capitadiscoverytnr
field than the database field itself.

a) If we're wanting to keep this as a datetime as opposed to a date without
time then we really need to ensure we return a timezone along with it.
b) The field name is misleading and non-standard for this sort of thing,
'updated_on' suggests a 'date' not a datetime.. 'updated' is a less specific
term which commonly denotes a timestamp as opposed to a date.

My point really is that the API should NOT simply reflect the database.. an API
is meant to hide the data storage details and rather expose the 'objects' and
'methods' an api consumer can work with.  Understanding of implementation
details should not be required or indeed cared about by an api consumer.

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


More information about the Koha-bugs mailing list