@jamesone http://blog.chilon.net/node/javascript/2017/03/03/on-node-orm2.html

@ohjames you can promisify with bluebird e.g.

const Promise = require('bluebird')
const models = Promise.promisify(require('../models'))

models('yourDb', false).then(db => doSomethingWithDb)

You might also need to set the context right e.g.

var redisGet = Promise.promisify(redisClient.get, {context: redisClient});
redisGet('foo').then(function() {
    //...
});

...but yes this is a pain and you also should really read this and then decide to use python and django instead 😄 . If you stick with node, sequelize looks good, loopback a more full featured option. I actually find orm2 useful for my purposes apart from lack of promise support.

You can't promisify with bluebird though, well only partially, due to #773 and see also rafaelkaufmann/q-orm#1.

For many reasons orm2 is a terrible choice, thankfully I'm not working with the client who made me use it anymore ;) sequelize is better, I will check out loopback, but honestly I'm starting to feel that ORMs often aren't a good idea and there's plenty of recent articles by people who feel the same.

Python/Django is pretty cool, used it a lot. Slightly prefer rails to Django though, much terser code due to ruby's advanced metaprogramming. Node is still cool though, despite the lack of mature ORMs, with recent projects I've been using rethinkdb without an ORM and finding there's less boilerplate when I'm just writing my joins directly.

const doSomethingAsync = Promise.promisify(db.models.my_model.create, {context: db.models}) is working fine for me in addition to the example i gave above, it can be done even if prototypes are not exposed but ok even this relies on access to methods on objects (the inconsistent API is a real problem). Thanks for reference to q-orm issue. Currently i do have to use orm2 but i'm going to raise exploring other options while the API i'm working on is still fairly contained.

Loopback is good (and worth bearing in mind it's a framework not just an ORM) but like anything there are drawbacks, context handling was an issue for me but i think they are improving that in 3.0.

I want to take a look at rethinkdb and not using ORMs is an interesting approach, I guess it depends on the ORMs available.