You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When saving a date using CRUD, the date is converted to GMT, which is correct. When it comes back it is converted to Current Time zone, which is nice, except that the Swift Date Object saves the corrected date with a zeroed time zone. So, if I were to pull a date from the datebase, and then resave that date into the database into a new date field, by timezone has now incremented by the factor of my current time zone. For instance, I'm in the US/Easter Time Zone. Depending on the month, I'm either GMT -0400 or -0500. So, my dates get corrected to +4 or +5 hours, then saved. When pulled, referenced in CRUD and saved to a new location, then it is again adjusted +4 or +5 hours. While it is quite convenient to have current timezone corrected dates coming in, I would suggest not correcting it for this very recursive error.
The text was updated successfully, but these errors were encountered:
When saving a date using CRUD, the date is converted to GMT, which is correct. When it comes back it is converted to Current Time zone, which is nice, except that the Swift Date Object saves the corrected date with a zeroed time zone. So, if I were to pull a date from the datebase, and then resave that date into the database into a new date field, by timezone has now incremented by the factor of my current time zone. For instance, I'm in the US/Easter Time Zone. Depending on the month, I'm either GMT -0400 or -0500. So, my dates get corrected to +4 or +5 hours, then saved. When pulled, referenced in CRUD and saved to a new location, then it is again adjusted +4 or +5 hours. While it is quite convenient to have current timezone corrected dates coming in, I would suggest not correcting it for this very recursive error.
The text was updated successfully, but these errors were encountered: