db.load vs orm.express

I have a single models.js module that I’d like to load in both Express request handlers and non-Express code. It would be nice if the function definitions for these two cases could be similar so that the models.exports function could be written once well.

Express expects a function with db and models as an argument:

define: function (db, models) {
    models.person = db.define("person", { ... });
}

On the other hand, db.load wants to pass just a callback:

db.load("./models", function (err) {
    // loaded!
    var Person = db.models.person;
    var Pet    = db.models.pet;
});

[ptnplanet]

I just want to share my solution:

File stack.js

require defineModels = require('./model').define;
app.use(orm.express('sqlite://sqlite3.s3dbt', { define: defineModels }));

File model.js

var async = require('async'),
    definedModels;
module.exports.define = function (db, models, next) {
    definedModels = models;
    var curriedLoad = function (file) { return function (cb) { db.load(file, cb); }; };

    async.waterfall([
            curriedLoad('.model/user'),
            curriedLoad('.model/posting'),
            // ...
    ], function (err) {
        db.models.user.hasMany(db.models.posting);
        db.sync(next);
    });
};

// I use passport.js and need models without being able to access them through the request object.
module.exports.model = function (name) {
    return definedModels[name];
}

[dresende]

This will pass to the readme or the wiki as soon as we release a new version.