Skip to content

MySQL dialect incompatible with BigQuery with LIMIT since #189 #198

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

Closed
vitaminmoo opened this issue Apr 22, 2025 · 3 comments
Closed

MySQL dialect incompatible with BigQuery with LIMIT since #189 #198

vitaminmoo opened this issue Apr 22, 2025 · 3 comments

Comments

@vitaminmoo
Copy link

#189 moved LIMIT and OFFSET to use positional arguments. Unfortunately as per the bigquery documentation:

Note that a query can use positional or named parameters but not both.

This results in queries with named parameters and LIMIT/OFFSET resulting in googleapi: Error 400: named parameter and positional parameter cannot be used together, jobInternalError from the server where on v1.33.0 they succeeded.

#170 specifies that GoogleSQL is expected to be an alias of MySQL, but this appears to be a difference.

@huandu
Copy link
Owner

huandu commented Apr 23, 2025

There is a new flavor Doris in the latest version. It's basically an alias of MySQL except that it doesn't use parameters in LIMIT/OFFSET. You can try this flavor and let me know whether it works for you. If so, I can add another flavor BigQuery with the same settings like Doris for your case.

@vitaminmoo
Copy link
Author

Will try and let you know.

@vitaminmoo
Copy link
Author

This appears to work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants