Austin Bonander

If you're using SQLx 0.7 then you need to install a compatible version of `sqlx-cli`. For example, `cargo install [email protected]`.

However, there's also this issue: https://github.com/launchbadge/sqlx/pull/3931#discussion_r2214203657

This kind of situation is likely better handled by disabling prepared statement caching at the connection level, which can be done by setting the statement cache capacity to zero: https://docs.rs/sqlx/latest/sqlx/postgres/struct.PgConnectOptions.html#method.statement_cache_capacity...

Yeah, sorry if I was a little ambiguous there. I meant to say that `statement_cache_capacity=0` _should_ force these statements to be prepared with the unnamed statement but it does not...

> Move the nullable columns logic in sqlx-postgres to the DB instead, removing the need to parse any query plans on the library side. This pessimizes every single query macro...

I believe this is because `psql` never sends parameter types when it prepares a query, so `$1` in that case gets inferred to be `citext`. However, we send the parameter...

@tgrushka #3939 was closed as fixed by the merging of #4009 which is now available in the `0.9.0-alpha.1` release. Unfortunately, we don't have the bandwidth to backport fixes to previous...

You're welcome to continue experimenting with this, but there's no point in merging this until it's stabilized as a target for `rustc` itself. We don't have the bandwidth to maintain...

This query executes on a different connection since you pass the `Pool` as the executor: ```rust let data: String = sqlx::query_scalar("select 'hello world from pg'") .fetch_one(&pool) .await .map_err(internal_error)?; ``` I...

Possibly fixed by #3980 which is now available in `0.9.0-alpha.1`