[Pg] Fix all datetime mappings #1657
Closed
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
|
Still having problems with #1113 |
|
I'll close this PR and re-open it because I though #1113 was related to the rest but it has to be done on another PR. |
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 PR will close #806, close #971, close #1113, close #1176, close #1185, close #1407 and close #1587.
Most are the same. The problem is pastgres.js, it didn't have a clear way of replace the default parsing into a
Dateobject after the client have been instantiates.I spent some time researching and found a solution.
Although it looks like postgres.js is still trimming the microsecond precision, even after bypassing the parsing.
I'll look into it further and possibly submit a new PR.
Added tests on all/most drivers that use postgres.