Austin Bonander
Austin Bonander
This is possible to trigger if you use `Executor::query()` with a query string instead of `sqlx::query()`, _et al_ (or the macros), as that uses the singular `Query` command which gets...
This should have been resolved by #3411. If anyone is still encountering this problem with the latest release, please open a new issue.
It's generally just me, and I get to it when I get to it.
Something that I ran into while implementing the multi-tenant example is how to make it more convenient to run migrations from multiple crates at once, with any of them possibly...
It's occurred to me that the `sqlx-toml` feature may not be desirable as a default since it's not strictly necessary for downstream library crates, and would be difficult to disable...
This would appear to be a bug, yes.
From Trino's own documentation: https://trino.io/docs/current/overview/use-cases.html > Do not mistake the fact that Trino understands SQL with it providing the features of a standard database. Trino is not a general-purpose relational...
Please provide a list of the options you need. Many of them shouldn't be configured in the URL, like extensions; the application needs to specify the extensions it's expecting.
@reasv this can happen if the database server returns columns in a different order than the server it was compiled with. I see your `SELECT` starts with `posts.*`, I recommend...
It's not really documented, but the query macros will accept a query string in fragments separated by `+`. This is specifically to support the generation of query strings by macros....