🐚 An async & dynamic ORM for Rust
Talking about synchronized schema, you can take a look at this PR (SeaQL/sea-orm#241). Like what you have said, the changes in database schema might cause unexpected compile error / behaviour in production. And this is what holding us back on this feature.
I've been bitten a few times by https://typeorm.io. The schema is declared in Entity class definitions. When the application connects to the database and the 'synchronize' option is enabled, the Entity definitions are compared to the DB schema and the DB schema columns are added/removed accordingly. This approach seems nice for development, but once an application hits production, it is easy to commit a change with synchronize=true, or to connect to a prod database with a development release. The risk is unexpected changes the schema, which could drop columns and cause chaos. IIRC, this is also a risk with SQLalchemy.
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
Looking for a mature alternative to TypeORM
3 projects | reddit.com/r/typescript | 5 May 2022
It's Prisma Time - Introduction
3 projects | dev.to | 13 Dec 2021
Preferred SQL ORM
6 projects | reddit.com/r/node | 16 Oct 2021
EF vs Dapper - a false dilemma
3 projects | reddit.com/r/dotnet | 27 Aug 2021
How to migrate database data in production?
2 projects | reddit.com/r/node | 26 Aug 2021