Victor Nordam Suadicani

>It is also possible to use the derive macros manually though I am not sure how smooth that experience is. The thing that ruins the experience of this the most...

I just realized that #427 is actually a very similar, if not identical issue to this that I hadn't seen previously.

Is this still a problem? I just tried this small test and it seems to work fine (prints "Got notification" every second). I don't need to do any dummy queries....

I think stuff like Miri and the LLVM tools shouldn't be in a CI profile by default. Those are only useful when writing unsafe code or FFI probably. I'd say...

> And clippy is only useful if you actually think its lints are useful to gate CI on, which many programmers do not. And many repos which still need CI...

Is it not possible to just make it so you could run `cargo sqlx prepare --database-url ...` multiple times, one time for each database? First time you run it, half...

Wouldn't specifying multiple database-urls in a single `cargo sqlx prepare` call as I suggsted above fix that? Then you can still remove any existing files before replacing the query JSONs....

For anyone else stumbling on this issue from search engines, just don't use `` `...` `` and instead use `#raw("...")`. Then you can do usual escaping in the string as...

I just ran into this as I tried doing something like this: ```rust trait FieldName { const FIELD_NAME: &'static str; } #[derive(Serialize, Deserialize)] struct MyStruct { #[serde(rename = T::FIELD_NAME)] renamed_field:...

I'm also having this problem with multi-file setups and it's kind of making the extension unusable for me at the moment.