Tim Sweña (Swast)

Now that we have some Geometry support in the `google-cloud-bigquery` library, I think this is a reasonable request. We may just need to pass `geometry_as_object=True` if available (necessary library versions...

Are there other properties besides `dryRun` that should be sent?

I think a general “update” call would be a good way to implement this. We’d probably want some checks for duplicate values. I think the current implementation checks that query...

I believe I might have fixed this issue in https://github.com/pydata/pandas-gbq/pull/152. I'll add a test to try out a `"dryRun": True` query before closing this issue.

Unfortunately even with #152, still can't do dry run queries because it raises when google-cloud-bigquery tries to fetch the results. Test code (query from [analyzing PyPI downloads](https://packaging.python.org/guides/analyzing-pypi-package-downloads/#counting-package-downloads)): ```python def test_configuration_with_dryrun(self):...

I've confirmed that `dryRun` queries do work upstream in https://github.com/GoogleCloudPlatform/google-cloud-python/pull/5119 . I think pandas-gbq will need to check for dry run queries and decide not to try to fetch the...

> Should we go the monorepo(ish) route and bring all backends into the ibis-project/ibis repository? There was an effort a while ago to move in the opposite direction. It's hard...

> How would we test these systems in our CI? I believe all of these backends are proprietary and require some kind of registration and/or credentials. This makes automation and...

Great suggestion. I think we do a "set difference" in order to discover schema mismatch, so this should be possible to figure out and include in the exception.

I'm a bit wary of including this information in the actual exception message due to potential privacy issues around logging. Instead, I'm adding `local_schema` and `remote_schema` properties to InvalidSchema in...