Skip to content

deps(cargo): upgrade sqlx from 0.8 to 0.9#167

Open
zefr0x wants to merge 2 commits into
SeaQL:masterfrom
zefr0x:sqlx-v0.9-migration
Open

deps(cargo): upgrade sqlx from 0.8 to 0.9#167
zefr0x wants to merge 2 commits into
SeaQL:masterfrom
zefr0x:sqlx-v0.9-migration

Conversation

@zefr0x
Copy link
Copy Markdown

@zefr0x zefr0x commented May 22, 2026

sqlx had a breaking change in its cargo build features that is ported to sea-schema in a compatible way. Old features should be documented as deprecated in the next release's changelog.

As per sqlx's MSRV policy, the supported Rust version is 1.94.0.

PR Info

  • Closes

New Features

Bug Fixes

Breaking Changes

Changes

  • Upgrade sqlx to 0.9
  • New tls-* cargo features were exposed from sqlx.

@zefr0x zefr0x changed the title deps(cargo): upgrade sqlx from 0.8 to 0.9 deps(cargo): upgrade sqlx from 0.8 to 0.9 May 22, 2026
`sqlx` had a breaking change in its cargo build features that is ported
to `sea-schema` in a compatible way. Old features should be documented as
deprecated in the next release's changelog.
@zefr0x zefr0x force-pushed the sqlx-v0.9-migration branch from 4bbed4f to 31a2745 Compare May 23, 2026 11:31
Comment on lines 30 to +41
@@ -38,7 +38,7 @@ impl Connection for Executor {
async fn query_all_raw(&self, sql: String) -> Result<Vec<SqlxRow>, SqlxError> {
debug_print!("{}", sql);

Ok(sqlx::query(&sql)
Ok(sqlx::query(AssertSqlSafe(sql))
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using this API means that you have made sure that the string contents do not contain a SQL injection vulnerability. It means that, if the string was constructed dynamically, and/or from user input, you have taken care to sanitize the input yourself. SQLx does not provide any sort of sanitization; the design of SQLx prefers the use of prepared statements for dynamic input.

Ref: https://docs.rs/sqlx/0.9.0/sqlx/struct.AssertSqlSafe.html

@zefr0x zefr0x marked this pull request as ready for review May 23, 2026 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant