avoid using ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP #158
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
|
Hello, I've added another solution to this problem in the regarding issue #265. Then I've found your commit here and tested your changes in a production environment. The time difference in grid view and in detail view disappeared. But when you check the log table you will still see a difference. To be 100% sure, I also checked the server logs. The times are identical to the times stored in the log table. Therefore, I am convinced that your solution is not entirely correct. |
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.
This exposes you to the timezone set in the database.
+fix log_at to use utc timestamps
+fix back link on log view