After being frustrated with Diesel, I gave a try to SeaORM and I couldn’t be happier (have been using it for more than a year). It is not perfect but certainly the best ORM I have ever used myself (vs Diesel, ActiveRecord, SQLAlchemy)
How come? I’m new to the space and picked Diesel a couple weeks ago for a new project because it seemed the most recommended. What do you prefer about SeaORM?
To me, SeaORM feels like a well-designed library while many things in Diesel feel like an afterthought or a hack. Which mostly manifests itself when doing something complex and debugging it.
That feels like a weird requirement to me; an ORM is by its very nature not going to be able to validate queries at compile-time.
And even if you're writing queries directly, any time you need to write something dynamic, you're not going to be able to verify those at compile-time either.
kstrauser|1 year ago
Simpliplant|1 year ago
Also recommend reading https://www.sea-ql.org/SeaORM/docs/internal-design/diesel/
satvikpendem|1 year ago
kelnos|1 year ago
And even if you're writing queries directly, any time you need to write something dynamic, you're not going to be able to verify those at compile-time either.