You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: read_gbq supports extreme DATETIME values such as 0001-01-01 00:00:00 (#444)
* fix: read out-of-bounds DATETIME values such as `0001-01-01 00:00:00`
deps: require google-cloud-bigquery 1.26.1 or later
* feat: accepts a table ID, which downloads the table without a query
* revert tests for read_gbq fix which isn't yet resolved
* Revert "revert tests for read_gbq fix which isn't yet resolved"
This reverts commit 2a76982.
* add todo for next steps
* add unit test for table ID read_gbq
* add helper for is_query
* implement read_gbq with table id
* fix remaining tests, don't localalize out-of-bounds timestamp columns
* Update pandas_gbq/gbq.py
* fix 3.7 unit tests
* correct coverage
* skip coverage for optional test skip
* fix docs build
* improve test coverage for error case
* as of google-cloud-bigquery 1.11.0, get_table before list_rows is unnecessary
* refactor tests
* add more scalars
* add more types
* add failing time test
* add test for bignumeric
* add test for null values
* add epoch timestamps to tests
* add post-download dtype conversions
* add failing test for desired fix
* fix the issue with extreme datetimes
* fix constraints
* fix tests for empty dataframe
* fix tests for older google-cloud-bigquery
* ignore index on empty dataframe
* add db-dtypes to runtime import checks
* document dependencies
* remove TODO, since done
* remove unnecessary special case for empty dataframe
Fixes prerelease test run
* remove redundant 'deprecated' from comment
0 commit comments