-
Notifications
You must be signed in to change notification settings - Fork 125
Add support for DATETIME BigQuery type #69
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
Comments
I made a change over at the google-cloud-python libraries do some type inference for the DB-API interface. https://github.com/tswast/google-cloud-python/blob/3b7c505e39d5091db5f3d618f181886189c362b7/bigquery/google/cloud/bigquery/dbapi/_helpers.py#L64 pandas-gbq probably needs similar logic to disambiguate. |
The only differentiation we could do without schema input (ref #46) would be datetime / timestamp based on tz. Although if anyone wants to add Period support, which can represent |
I believe that you might want to try the data type TIMESTAMP instead. |
The PR at #25 uses the |
Closing since I believe this is fixed by #25 |
Re-opening as I noticed |
This would need to be supplied manually because there is no differentiation between these in native pandas types |
I believe that when |
I also noticed that when pulling a column with a query with:
generates a table with dtypes:
And takes up 8x the memory
|
Closed by #224 |
Recently a question was posted on Stackoverflow regarding support for
DATETIME
field type in BigQuery. I was wondering if it's possible to update the mapping that the methodto_gbc
does to also mapDATETIME
values.Thanks!
The text was updated successfully, but these errors were encountered: