extend feature to create tables from pyarrow objects to include datetime/time/timestamp types #606
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.
Summary
This PR addresses #605.
Specifically:
pa.date32()is now mapped toDate32pa.date64()is mapped toDateTime64(3)(preserving millisecond precision)pa.timestamp('s', tz=None)→DateTimepa.timestamp('s', tz='TZ')→DateTime('TZ')pa.timestamp('ms', tz=None)→DateTime64(3)pa.timestamp('us', tz=None)→DateTime64(6)pa.timestamp('ns', tz=None)→DateTime64(9)pa.timestamp('ms', tz='TZ')→DateTime64(3, 'TZ'), etc.Checklist
Delete items not relevant to your PR: