-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Unable to use prepared statements with go-sql-driver/mysql when connecting to StarRocks #1638
Comments
Link please?
I never use neither StarRocks nor JDBC. But when I googled, |
Thank you, I can use client-side prepared statements for now, but according to the documentation, client-side prepared statements still have a risk of SQL injection. StarRocks supports server-side prepared statements, and the documentation link is as follows: I would like to know why the busy buffer issue occurs when using server-side prepared statements. |
It is statement level prepared statement. It is different from protocol level prepared statement.
It is very low risk. And unless you are using
I don't know. busy buffer happens after some other errors. It is just a result, not a cause. |
And what version of starrocks do you use? |
ok,thank you for reply. |
|
For the record, I confirmed that prepared statement works with this driver and StarRocks 3.3.5. Do not assume what cause your error. Write complete step to reproduce instead. I can not reproduce your error because your example is no reproducible. (no step to prepare users table). |
Issue description
I am trying to connect to StarRocks using Go and the go-sql-driver/mysql library. According to the latest StarRocks documentation, it supports prepared statements. I have successfully used prepared statements with Java's JDBC, but when I attempt to use them with Go, I encounter an issue.
When I try to use prepared statements with the go-sql-driver/mysql library, I receive a "busy buffer" error. However, if I do not use prepared statements, everything works fine.
Example code
Error log
Configuration
*Driver version (or git SHA):v1.8.1
*Go version: v1.19
The text was updated successfully, but these errors were encountered: