Austin Bonander

That's unlikely to be something we can typecheck at compile time without performing our own analysis of the query.

I don't see a compelling reason to have this in SQLx. If you embed migrations in your application, you can have it execute any commands you want before running them....

> I can also update that if you think that's worthwhile to change. That sounds fine, yeah.

I was wondering if we could start with something like `.begin_with("BEGIN READ ONLY, READ COMMITTED").await` (on the `Connection` trait and `Pool`) which returns a `Transaction` since that would cover most...

@LukeMathWalker I think my proposal for `.begin_with("")` would be a good start: https://github.com/launchbadge/sqlx/issues/481#issuecomment-726991429 If nothing else it's something we can build on if it's not satisfactory.

I'm sorry that you feel that way. The main goal here was to just get everything out that was in my head rather than me continuing to fail at describing...

Yeah, I probably should have been more careful with my choice of words but it seemed like we were basically at an impasse anyways. It happens. As for prior art,...

I'm afraid I'm not familiar with the USE acronym you've been referencing and Googling it wasn't much help. I inferred that it stood for "Utilization Saturation Errors" and finally found...

If this is something that only just started happening, it sounds like a regression in Planetside.

We chose to enable `PIPES_AS_CONCAT` by default as an ergonomic choice, and to get MySQL to behave at least somewhat more closely to SQLite and PostgreSQL. While `||` is generally...