I've been thinking a lot about that stuff lately and I honestly think ormx is the perfect candidate to build on and iterate towards a full-fledged ORM.
The features I'd personally like to see are more or less the featureset of Sequelize, to be more accurate:
Number 3 would be pretty much just additional things to implement on Table and would be the most trivial
Number 1 is a tough one, as we need to find a way to synchronize tables before sqlx compiles and checks our queries.
For instance on an empty database, a model would try to compile its queries, but the table doesn't exist yet so compilation would fail.
Hey,
I've been thinking a lot about that stuff lately and I honestly think ormx is the perfect candidate to build on and iterate towards a full-fledged ORM.
The features I'd personally like to see are more or less the featureset of Sequelize, to be more accurate:
Number 3 would be pretty much just additional things to implement on
Table
and would be the most trivial Number 1 is a tough one, as we need to find a way to synchronize tables before sqlx compiles and checks our queries.For instance on an empty database, a model would try to compile its queries, but the table doesn't exist yet so compilation would fail.
I'm currently experimenting here: https://github.com/OtaK/ormx/tree/otak/schema-sync