https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39748
--- Comment #16 from David Cook <[email protected]> --- (In reply to Katrin Fischer from comment #14) > As the date is getting close again and it might take down multiple of our > instances (again) for a day... if we could find a fix before April 25 that > would be awesome. I do love a good DST bug but this one is a tricky one for sure. Since the error happens during search, it seems unlikely that the data is being changed during the search, so that's probably not the source of the problem. It could be a cronjob or it could be leftover from some other previous action. It would be good to know which column is involved in the problem. I suppose a person could set every timestamp/datetime in a patron record to 2025-04-25 00:00-00:59 and set the timezone to Africa/Cairo and work backwards from there... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. _______________________________________________ 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/
