jugglingdb
jugglingdb copied to clipboard
1602
Multi-database ORM for nodejs: redis, mongodb, mysql, sqlite3, postgresql, arango, in-memory...
Mixins lead to mess in big projects, it is better to not allow them at all. Business logic should not reside in models with the caveat for hooks and validations.
I'm looking at a node/express/mongoose [tutorial](https://gist.github.com/pixelhandler/1791080) where you could do this ``` javascript var Images = new Schema({ kind: { type: String, enum: ['thumbnail', 'catalog', 'detail', 'zoom'], required: true },...
Consider removing all instance methods and only have data in mode instances, ideally data should be sealed/frozen by default
- deprecate sync validations - callback with error only (reject promise) instead of collecting errors on instance - think of readable error messages instead of 'Validation error' - fail after...
It should be possible to add multiple hooks per action. Also let's get rid of mixin-style hooks declaration. Hook should return promise. ``` User.afterCreate = function(data, done) { Basket.create({userId: this.id},...
add populate feature, which is similar to include, that support where query. More details please refer to [./test/populate.test.js](https://github.com/Alvansea/jugglingdb/blob/feature-populate/test/populate.test.js)
Hi there, Is there a way to adjust the logging levels of what is outputted from the database. On my local machine and on heroku the logs have a lot...
Allow to specify engine in mysql in jugglingdb/mysql-adapter#102. It should break other sql adapters but it should be better that subclasses manage table options, etc... ?
