Tests: Explicitly use both TIMESTAMP {WITH,WITHOUT} TIME ZONE types
#439
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
mfussenegger
approved these changes
Jul 19, 2022
matriv
approved these changes
Jul 19, 2022
Makes sense specifically in the context when exercising date/time conversions from `TIMESTAMP` to corresponding Python types in the future.
amotl
force-pushed
the
amo/datetime-doctests-more-types
branch
from
ca93b68 to
1f5f30c
Compare
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.
As a followup to #438, I think it might make sense specifically in the context when exercising date/time conversions from
TIMESTAMPto corresponding Python types in the future, in order to set the stage for #437.