https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17621
--- Comment #2 from Martin Renvoize <[email protected]> --- 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. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
