You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
As I'm completing the rest of the interfaces for #243, I am feeling like I'm fighting the compiler a lot because Diesel's connector cannot be sent across async threads safely. It is frustrating but I wanted to open this issue so I can revisit the pros/cons later.
I'm using Diesel because I want compile-time checked queries, but also because it will manage sql migrations. Another feature is mapping custom Postgres enums to my own structs.
I see is sqlx. But it doesn't handle migrations and I'm unsure how it maps queries to my structs. Especially w/ my custom PG types.
I may be able to keep Diesel and use the tokio-diesel crate.
The text was updated successfully, but these errors were encountered:
As I'm completing the rest of the interfaces for #243, I am feeling like I'm fighting the compiler a lot because Diesel's connector cannot be sent across async threads safely. It is frustrating but I wanted to open this issue so I can revisit the pros/cons later.
I'm using Diesel because I want compile-time checked queries, but also because it will manage sql migrations. Another feature is mapping custom Postgres enums to my own structs.
I see is sqlx. But it doesn't handle migrations and I'm unsure how it maps queries to my structs. Especially w/ my custom PG types.
I may be able to keep Diesel and use the tokio-diesel crate.
The text was updated successfully, but these errors were encountered: