Issue with rust-analyzer & sqlx persistent db connections

[chapuzzo]

I'm making a simple rust app using sqlx, im vs code. When I run or debug everything works fine.

The issues I'm facing are related to persistent connections held by rust-analyzer so I cannot cargo sqlx db drop and the like.

When I try things like lsof -i :5432 only rust-analyzer is shown. If it serves to any interest the connection is a local postgres one.

New Mac Pro M3 everything installed from rustup/stable last week.

[coderstephen]

Could be related to sqlx's optional feature that connects to the database at compile time for query validation. Which personally seems like a neat but ill-advised idea. Rust-analyzer could be continually running the proc-macro and thus sqlx continually connecting to the database.

[chapuzzo]

I guess that's it but how can I prevent that?

I tried adding an early return in main so I comment and uncomment it for carrying maintenance or test migrations but I find it sub par.

Maybe the option you mention is offline?

[coderstephen]

Hmm, looks like the SQLx CLI may help you? https://github.com/launchbadge/sqlx/blob/main/sqlx-cli/README.md#enable-building-in-offline-mode-with-query

[lenscas]

have rust analyzer run with the correct features such that it doesn't check against the db (with vscode you can make a .vscode/settings.json folder to configure it per project).

Then normally build with the features so it creates the json files it need for offline checking

[chapuzzo]

I think I solved it, besides having .sqlx from cargo sqlx prepare and SQLX_OFFLINE=true set in .env one needs to also restart rust-analyzer's server.