Austin Bonander

A thought I had was to not have a `sql()` method on `InjectionSafe` and treat it like a true marker trait, then have `Q: AsRef + InjectionSafe` as the bound...

@autarch you might also be interested in this proposal https://github.com/launchbadge/sqlx/issues/1488 The main idea is to allow adding/removing parts of the query at runtime while still providing compile-time checks.

We actually just released support for the `options` parameter, either in the URL or set on [`PgConnectOptions`](https://docs.rs/sqlx/latest/sqlx/postgres/struct.PgConnectOptions.html#method.options). The reason the version using `sqlx::query()` hangs indefinitely is because Postgres doesn't support...

@andrewwhitehead would you prefer to finish your PR or just see this one merged? I would credit you both in the changelog.

> I have an older postgres, and the extra_float_digits is also not supported. Given time and support staffing, I'd have already moved to postgres 14, but at the moment, I'm...

It's an issue with the signature of `Migrator::run()` which I actually ran into while implementing #2001. To work around it I added `.run_direct()` which takes a mutable reference to a...

While executing `listen[_all]()`, `unlisten_[all]()` and any methods from `Executor`, the connection inside `PgListener` buffers all subscribed messages in the background and returns them in order the next time you call...

Right, so `tokio::select!()` breaks the connection because our futures don't support being canceled very well; it's an area we're actively refactoring for another beta release. Using `tokio::time::timeout` would have the...

Talked it over with @mehcode and we arrived on an interesting solution. We'd like to be able to attach a channel (such as `futures::channel::mpsc`) to `PgListener` for it to forward...

We can work on ways to address this. It could be something on `ConnectOptions` to tell the connection to automatically flush the prepared statements if it encounters this error instead...