sqlx VS diesel

I'm considering making my own wrapper over lower-level database drivers. There are a lot of features in sqlx that I don't need, and the latest version seems to have removed useful data structures that SQLPage is using. It also removed support for SQL Server.

sqlx to interface with multiple databases (I am considering moving to something else to support more databases, though)

The biggest thing to note in this release is the restructuring of the project and the removal of the MSSQL driver as it was not at the same maturity and usability level as the other drivers. As previously announced (https://github.com/launchbadge/sqlx/discussions/1616), we have plans to introduce a fully featured replacement as a premium offering, alongside drivers for other proprietary databases, with the goal to support full-time development on SQLx.

sqlx

Thanks for sharing your experiences. I've been looking to get into snowflake for some time (even opened this https://github.com/launchbadge/sqlx/issues/986) . We thought to move to it years ago, but there's no way it was going to replace a significant amount of the mariadb we're running, and unless it did I wasn't looking forward to managing 2 DBs.

however, a much worse problem is its inability to do dynamic queries. If you have two queries that only differ in a column name, you're forced to copy paste the entire query. You can try and hack around it, but it's ugly either way. Here's a good overview, with no really good solutions.

I did look at mysql initially. Then I started checking other crates. Diesel is an Object Relation Model (ORM), I'm not yet keen on taking on the complication of learning ORM, I give this crate a pass in the meantime.

I would recommend people look at diesel from Rust for how nice it could be. https://diesel.rs/ Look at the complex queries example. So much more readable and easier to understand.

Lemmy is written in Rust using Actix Web and Diesel.rs.

https://actix.rs/

https://diesel.rs/

for psql i feel like there's a wealth of things to choose from, like diesel perhaps https://crates.io/crates/diesel

Essentially you would need to implement Backend + Connection (+ the whole bunch of helper traits) for this type. That's ~1kloc for all of that. The PR that introduced this feature has more details on the exact implementation that's generated.

diesel

some things are barely expressible in the type system. For example, window functions are unavailable (the issue is six years old). You can use raw SQL, but then it has the same problems sqlx has

Have you considered using a library such as sqlx or Diesel? They’ll handle this for you and supports multiple backends

This is a patch release that contains several bugfixes. Notably it contains a workaround for a name resolution bug in rust-analyzer that affected diesel's DSL. With this rust-analyzer should be able to provide type hints and completions in many more cases than before, although there are still issues with specific constructs including queries containing .filter()/.inner_join() and .left_join() expressions. These are still not recognized correctly by rust-analyzer.

I can provide an example how to handle these kind of setup with diesel: https://github.com/diesel-rs/diesel/blob/master/diesel_dynamic_schema/tests/dynamic_values.rs