Fix default timezone to UTC for SQL database #1437
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
johannpinson
changed the title
|
@johannpinson Can you also update the documentation? What kind of values are allowed in this new settings |
|
@Aurelsicoko docs updated |
lauriejim
approved these changes
Jun 26, 2018
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My PR is a:
🐛 Bug fix
Main update on the:
Admin
Plugin
This PR fix the bug about timezone transformation when you save a date/datetime/time/timestamp with a SQL database.
I added the ability to change this settings, but in fact, I don't recommand it.
Do I have to change it?
It also contains an improvement for both type of database about the use of
.utc()in the admin.