The datetime precision with zero should be dumped #18883
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
`precision: 0` was not dumped by f1a0fa9. However, `precision: 0` is valid value for PostgreSQL timestamps.
sgrif
added a commit
that referenced
this pull request
Feb 11, 2015
…zero_for_postgresql The datetime precision with zero should be dumped
kamipo
deleted the
fix_datetime_precision_dumping_zero_for_postgresql
branch
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.
precision: 0was not dumped by f1a0fa9.However,
precision: 0is valid value for PostgreSQL timestamps.