I’ve been learning Nodejs and created a project as a applying knowledge go to project, "miniORM"
Its just a project that im planing to apply it in my future upcoming nodeJs project.
MiniORM offer immutable builder state management for creating SQL queries in simple, readable and clean API. It still relatively small and personal project.
Its support ES6 modules, singletone database connection through mysql2 pool. MiniORM model instance establish a shared connection to reduce the usage of the resources and automatically shutdown when a process closes or terminate
It offers promise based API, the core miniORM is promised based like as it query builder are chainable, awaited to delivery the results.
done() method is used to terminate the built query, run it against the connected …
I’ve been learning Nodejs and created a project as a applying knowledge go to project, "miniORM"
Its just a project that im planing to apply it in my future upcoming nodeJs project.
MiniORM offer immutable builder state management for creating SQL queries in simple, readable and clean API. It still relatively small and personal project.
Its support ES6 modules, singletone database connection through mysql2 pool. MiniORM model instance establish a shared connection to reduce the usage of the resources and automatically shutdown when a process closes or terminate
It offers promise based API, the core miniORM is promised based like as it query builder are chainable, awaited to delivery the results.
done() method is used to terminate the built query, run it against the connected Db, then return database insight.
But .done() method is optional since miniORM instance can be awaited, it knows when the chain ends and deliver the desired database insight.
The public API of miniORM is built to light, clean, readable and sounds just like an instruction
Like "Hey, miniORM model from table posts count records, where field post likes is between 5 and 50, done"
Done is optional