Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL CRUD Date Formatter recursive date/time increment #56

Open
videomyster opened this issue Nov 10, 2018 · 0 comments
Open

MySQL CRUD Date Formatter recursive date/time increment #56

videomyster opened this issue Nov 10, 2018 · 0 comments

Comments

@videomyster
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant