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
I'm trying to use sqlx to connect to a StarrocksDB. Checking the docs/forums, it doesn't support prepared-cache but it mentions that most MySQL clients should be able to disable that feature. I set statement_cache_capacity to 0 as the docs mention but I still get this error when trying to connect:
Error: Database(MySqlDatabaseError { code: Some("HY000"), number: 1064, message: "Getting analyzing error. Detail message: Set statement only support constant expr.." })
Can it be that setting statement_cache_capacity to 0 does not disable the prepared-cache?
Thanks!
Minimal Reproduction
use sqlx::mysql::MySqlConnectOptions;use sqlx::ConnectOptions;#[tokio::main]asyncfnmain() -> Result<(),Box<dyn std::error::Error>>{let _pool = MySqlConnectOptions::new().host("127.0.0.1").username("root").database("my_db").port(9030).statement_cache_capacity(0).connect().await?;Ok(())}
Info
SQLx version: 0.7.4
SQLx features enabled: ["runtime-tokio", "mysql"]
Database server and version: StarrocksDB (MySQL)
Operating system: macOS
rustc --version: 1.77.2
The text was updated successfully, but these errors were encountered:
Bug Description
I'm trying to use
sqlx
to connect to a StarrocksDB. Checking the docs/forums, it doesn't support prepared-cache but it mentions that most MySQL clients should be able to disable that feature. I setstatement_cache_capacity
to0
as the docs mention but I still get this error when trying to connect:Error: Database(MySqlDatabaseError { code: Some("HY000"), number: 1064, message: "Getting analyzing error. Detail message: Set statement only support constant expr.." })
Can it be that setting
statement_cache_capacity
to0
does not disable the prepared-cache?Thanks!
Minimal Reproduction
Info
0.7.4
["runtime-tokio", "mysql"]
StarrocksDB (MySQL)
rustc --version
:1.77.2
The text was updated successfully, but these errors were encountered: