Move date/time handling to NodaTime #41

New Issue

2022-08-07T23:51:47Z

danieljsummers commented

2022-08-07 23:51:47 +00:00

(Migrated from github.com)

v7 already uses NodaTime to convert dates/times from UTC to the small group's local time. When upgrade to v8, we ran into an issue that was exposed by a new version of Npgsql. In researching the text around this, rather than go through and put DateTimeKind on all the various dates and times, convert these to use NodaTime constructs.

This affects prayer request entered and updated dates, as well as user last seen date/times. Ensure that queries for "current" and "expired" requests take the small group's time zone into account when they query this data.

(This is probably the root of the #22, which itself arose from #17... These implicit conversions have been "bug"ging this project for years.)

v7 already uses NodaTime to convert dates/times from UTC to the small group's local time. When upgrade to v8, we ran into an issue that was [exposed by a new version of Npgsql](https://www.npgsql.org/doc/release-notes/6.0.html#timestamp-rationalization-and-improvements). In researching the text around this, rather than go through and put `DateTimeKind` on all the various dates and times, convert these to use NodaTime constructs. This affects prayer request entered and updated dates, as well as user last seen date/times. Ensure that queries for "current" and "expired" requests take the small group's time zone into account when they query this data. _(This is probably the root of the #22, which itself arose from #17... These implicit conversions have been "bug"ging this project for years.)_

danieljsummers commented

2022-08-17 01:10:09 +00:00

(Migrated from github.com)

This is complete, and handles expiration properly (the day a request is entered is "day 0"). This will be part of version 8.

Sign in to join this conversation.