https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36217
--- Comment #17 from David Cook <[email protected]> --- (In reply to David Cook from comment #16) > Of course, an alternative fix would've been to just treat the incoming > timestamp as UTC and then convert it, but datetime math can be complicated. > That would've been a more flexible solution, but also a more complicated one. Of course, now that I look at it again, Jonathan might have a point. We solved this 1 problem, but the real problem is that the API server handles all incoming dates according to the DB's local time zone (if only using DBIx::Class and no additional handling). I've said for years that storing timestamps in a local timezone in Koha was madness/problematic, but we've mostly just ignored that warning. Of course, the problem is so systemic that I don't know how feasible it is to actually fix it in Koha. Yet, expecting every API consumer to know the timezone of the DB server is also not great... There might be some DBIx::Class magic we can do to automatically detect any date field and automatically convert timezones, but I hate magic. It ends up being messy and difficult to maintain. I think that's why we went with this solution for this bug. The alternative was just too overwhelming. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
