-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: fixed a bug that all TIMESTAMP fileds become 00 secconds. #148
Conversation
Codecov Report
@@ Coverage Diff @@
## master #148 +/- ##
===========================================
- Coverage 75.5% 29.43% -46.08%
===========================================
Files 8 8
Lines 1535 1546 +11
===========================================
- Hits 1159 455 -704
- Misses 376 1091 +715
Continue to review full report at Codecov.
|
This looks great! Thank you. Could you add a short test? |
aba23d0
to
69147dd
Compare
pandas_gbq/tests/test_gbq.py
Outdated
test_size = 6 | ||
df = DataFrame(np.random.randn(test_size, 4), index=range(test_size), | ||
columns=list('ABCD')) | ||
test_timestamp = datetime.now(pytz.timezone('UTC')) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally this would be a value rather than .now
, and that's harder to reproduce, but not a huge issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your review. I fixed this.
05ac27b
Integration tests pass: https://travis-ci.org/maxim-lian/pandas-gbq/builds/352690707 |
@maxim-lian @rhoboro Thanks a bunch! |
Fixed a bug that all TIMESTAMP fileds become 00 secconds in BigQuery.
#69 (comment) mentions to same issue.