Closed jondot closed 1 month ago
+1 on the ownership issue. Multiple people are running into #13. Consumers of API shouldn't need to worry about your library's lifetimes
Auto migration ("syncing" a schema, as well as versioned, additive migrations)
There are several crates for this thing, maybe Toasty can integrate or reference them:
Hi @carllerche This is an exciting project coming from tokio. I've been building loco.rs which I hope fills in the "productivity" part for Rust (referring to that section in your blog post). We're using SeaORM, which is stable and feature rich, and serves us well so far.
Here are some things I looked for when I evaluated SeaORM (against Diesel, sqlx-macros, etc.), I hope to offer (not to push) some insight for Toasty:
// let me extend logic onto my fetched entities to keep logic tied to data let user = User.find(..) if user.has_billing() { //... }