actix_sqlx_mysql_user_crud VS SccaSoloPointsCalculator

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.

I wanted to challenge myself if I could do it, and I think I managed. Feel free to check out the diff here. Getting rid of dyn and all these smart pointers should even improve runtime performance and reduce heap allocations. There is quite a bit of boilerplate with regards to the generics, but that kinda comes with the territory in Rust if you absolutely want to do dependency injection, by default, always, everywhere.