rocket_auth VS sqlx

The basic CRUD operations are done, however I'm still missing the users and authentication logic. Since I don't want to build it form scratch if possible, I found rocket_auth which seems perfect, except that it does not support diesel.

There is https://github.com/tvallotton/rocket_auth, which salts by default IIRC

Perhaps Rust has some nice crates that will assist your development, but you're going to have to evaluate whether their design decisions meet the needs of your design, especially if you want to handle powerloss without data loss whilst maintaining high performance. Here's an example of where a create chose design over performance https://github.com/launchbadge/sqlx/issues/2007

SQLx's query macros act like format macros, and the database is apparently smart enough to not treat bind parameters as part of the SQL.

> Doesn't it need to run introspection queries to check the table structures?

Yes, but it can also run in 'offline' mode where it builds against saved metadata [0]

0: https://github.com/launchbadge/sqlx/blob/main/sqlx-cli/READM...

well it does have its usecases. e.g. https://github.com/launchbadge/sqlx

I felt the same way until I found sqlx (https://github.com/launchbadge/sqlx). The package lets you write sql in your app with compile-time checks. Was so much easier to get up and running than learning a new ORM.

If writing SQL directly, what process do you use to update your queries during schema changes? Do you rely on a test suite to catch errors then update queries by hand? Are you using compile-time checks through libraries like sqlx [1]?

[1]: https://github.com/launchbadge/sqlx

You probably know about this already but we've finally landed the change to one file per query in offline mode which should provide both performance and ergonomic improvements, especially when it comes to merging multiple Git branches that change queries.

What I really like about it (apart from being a really nicely designed language, that is very expressive, powerful, performant and one of the safest because of the strict typing/memory management), is that you can kind of focus on just programming, without all the hassles around setting up a project, thinking about building/deploying etc. as tooling is really awesome as well (rust-analyzer, cargo, crates.io etc.). Libraries are usually high-quality and innovative (which is IMHO not so true for a lot of different other languages, including the ones you mentioned). E.g. if you want to create a web-server/API you could try something like this (my current recommendation): https://github.com/tokio-rs/axum and https://github.com/launchbadge/sqlx for good integration of typed sql in Rust or if you want something higher level: https://github.com/SeaQL/sea-orm

It doesn't allow you to install third-party binaries, but it allows you to make your own binaries runnable with something similar to npx. And, as sqlx-cli is also available as a library, you can make an xtask which just runs that.