eggjs orm plugin specification

Created on 15 Feb 2017 · 22Comments · Source: eggjs/egg

Now there are more and more orm framework requirements, most orm framework are Active-record-pattern-like(https://en.wikipedia.org/wiki/Active_record_pattern), similar to the view plugin(https://eggjs.org/zh-cn/advanced/view-plugin.html), we need a specification for egg orm plugin.

Orm framework generally has the following features:

transform table to object, and use files under app/models to define.
Relationship between several tables.
Syntactic sugar for query, update, delete etc.
...

So let us discuss whether a specification is needed or not?

discussion

Source

jtyjty99999

Most helpful comment

I have developed an ORM, Modelar, I recommend have a look at it, may satisfy egg needs, support MySQL/MariaDB, PostgreSQL, SQLite, MsSQL, OracleDB and DB2, similar to TypeORM, but written in pure JavaScript.
https://github.com/hyurl/modelar
Give me notice if you'd like it or have any suggests.

A demo has been published at cnode.org, please visit:
https://cnodejs.org/topic/5a27b1add92f2f5b185acc68

hyurl on 3 Dec 2017

👍6

All 22 comments

currently, we got:

@popomore should we need proposal label?

atian25 on 15 Feb 2017

@atian25 maybe RFC

popomore on 18 Feb 2017

Current we have https://github.com/eggjs/egg-labels/blob/master/labels.json

popomore on 18 Feb 2017

Now we see some points in specification:

Directory for defining data models like app/model or app/models
File name specification for data model
How to access data model, by ctx/app
plugin pattern
- config
- heartbeat request
- tracelog
- event handle like onerror, ondisconnect, onconnect

jtyjty99999 on 23 Feb 2017

only use app/model, not s

atian25 on 24 Feb 2017

https://github.com/tgriesser/bookshelf

popomore on 27 Feb 2017

https://github.com/balderdashy/waterline
Waterline is a next-generation storage and retrieval engine, and the default ORM used in the Sails framework
It provides a uniform API for accessing stuff from different kinds of databases, protocols, and 3rd party APIs. That means you write the same code to get and store things like users, whether they live in Redis, MySQL, MongoDB, or Postgres.