After testing both SeaORM & Tokio Postgres:
With both, you still need to manually write
- junction table
- migrations
- mappings to your useful or complex types/structs.
So basicaly you just get almost raw result from a database that is a SQL table representation that you transform to you business models.
Here I see that SeaORM is just some added burden. I see no benefit in using it for my project.
You need to learn their API (DSL) to query the database.
It names its stuff "entities" and "models" and you have to come up with another name for your business models.
Extremely difficult to work with relation ships. Even harder if you models have multiple or chained relation ships.
With Tokio Postgress it is easier: sur we get to write our own migrations and junction tablles, but we only do it with SQL.
No need for a ton of dependencies.
Just use your SQL knowledge
Easy to work with complex, multiple and chained relations ships: you just do as much LEFT JOINS as you want.
The casting for the Row result to your business models is easier.
3x more performance over SeaORM in most cases in my project.
التنينوكس