-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Error processing job with UNNEST and query parameters #234
Comments
This issue appears difficult to fix given the current design, so it might be better to temporarily use an alternative method or a workaround. As a workaround, you can use CAST. Although it becomes redundant when running on the actual BigQuery, casting to the appropriate type can avoid the problem in many cases. (not all, though)
The cause of this issue can be summarized as follows: |
It seems that ZetaSQL allows us to specify query parameter types in the In goccy/go-zetasqlite#207 I used a context key to pass along an option to the driver. It seems that is an antipattern in Golang, but I wonder if we could do something similar. Another option would be to expose a method on the zetasqlite connection interface for specifying these values, like we do with |
Steps to reproduce:
I don't know if the issue comes from here or from zetasql
The text was updated successfully, but these errors were encountered: