actix_sqlx_mysql_user_crud VS diesel

Lastly, I wrote a CRUD a while ago that's on the Actix Web examples, which is a simple CRUD that has full test coverage. I didn't do any mocking, but you can take a look at the code and see if any of the TDD patterns I used are helpful.

actix sqlx mysql user crud

If you want an idea of what you'd be getting into, take a look at this example CRUD I wrote w/ actix-web, sqlx, and serde: actix sqlx usercrud

I use the pool here

I use the pool here ``` use super::{Group, User}; use sqlx::mysql::MySqlRow; use sqlx::{FromRow, MySqlPool}; use std::sync::Arc;

This is how I did a CRUD using Actix and SQLx. I, personally, did not use compile time queries. They are a good concept, I just think they need to be wrapped behind framework where they can be switched on an off by a macro or something like that.

Let the best practice win. I made this CRUD modular with full test coverage: https://github.com/jamesjmeyer210/actix_sqlx_mysql_user_crud

I don't have a direct answer for you but I think the best way to solve this would be to write extensive test coverage to verify the behavior of your middle-ware. Here is a CRUD application I build with full test coverage that is listed as an example on the Actix Example repo. Feel free to use the tests I wrote as a template for your own.

7. Diesel

Both seem nice. However, both of them rely very heavily on prepared statements. Unfortunately, using prepared statements is a no-go when you use connection poolers like pgbouncer, or in my case AWS RDS proxy. A discussion in Diesel indicates that disel is not going to provide any support for disabling prepared stements (https://github.com/diesel-rs/diesel/discussions/3575), and a discussion on sqlx hints that disabling prepared statements is possible, but I haven't found any documentation or examples for it.

In addition we are experimenting with prebuild versions of diesel-cli that can be installed directly. We have a set of prebuilt binaries here. We are interested in feedback about how the provided binaries work on your platform.

First of all thanks for making this great tool. As it happens I currently toy around with using it for diesel-cli releases. See the WIP PR here. I think diesel-cli is a good example of a tool that depends on system libraries as it needs to link native database drivers, so this new release is welcome. Defining the dependencies seems to allow easily building things on x86_64-unknown-linux-gnu and x86_64-apple-darwin. It seems to pick up everything in the right way there.

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.

Most wanted missing features in diesel

There are two problems with using Rust for web servers:

1. The only production-ready Rust web servers require writing async request handlers. Async Rust is not fun.

2. The only good Postgres client library is async: https://crates.io/crates/sqlx

I'm trying to remedy the first problem with https://crates.io/crates/servlin .

Solving the second problem will be another project. I hope someone else does it. There is https://crates.io/crates/diesel but it has the same problem as async Rust: incomprehensible compiler errors.

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

https://actix.rs/

https://diesel.rs/