I used to store all dates in UTC, yet had my app timezone set to where I’m at. I would then use that to convert relevant dates at the very last moment (i.e., in the view). But … cursor pagination uses your app’s timezone setting to produce its SQL; hence the error. So I now have my timezone set to UTC and will use a user-specific setting for displaying dates and times! Seems we’re good again.
3 responses to “Turns out Laravel’s just added cursor pagination. (Yay!)”
Guess it doesn’t always “just work.” ☹️
I used to store all dates in UTC, yet had my app timezone set to where I’m at. I would then use that to convert relevant dates at the very last moment (i.e., in the view). But … cursor pagination uses your app’s timezone setting to produce its SQL; hence the error. So I now have my timezone set to UTC and will use a user-specific setting for displaying dates and times! Seems we’re good again.
On the one hand: this is nice. On the other: sucks that this is still different from how Microsub likes things.