continuation local storage context lose in bookshelf promises

continuation-local-storage in nodejs is similar to thread local storage in java but is based on chains of Node-style callbacks instead of threads.

continuation-local-storage provides a namespace to set variables. When I try to access these variables inside ‘then’ function of any bookshelf promise,the Namespace loses the active context and I could not find these variables.

My first middleware for each request

var cls = require('continuation-local-storage');
app.use(function (req, res, next) {
    var namespace = cls.getNamespace('my session');
    bookshelf.transaction(function (tx) {
        namespace.run(function () {
            namespace.set('transaction', tx);
            next();
        });
    });
});

My next middleware

var namespace = require('continuation-local-storage').getNamespace('my session');
namespace.get('transaction')   // transaction defined
new EntityModel({id:1})
.fetch()
.then(function(){
     namespace.get('transaction') //transaction undefined
})

Can you give me any idea about the promise library used by bookshelf so that I can try to override it’s ‘then’ function to bind namespace with ‘then’?

[ricardograca]

No idea what you’re talking about. Can you be more clear about what that continuation-local-storage is?

Also, this seems like it’s not related to Bookshelf at all. You are calling that namespace.get() thing with a string in the first case and with a variable in the second, which I assume is indeed undefined, since you probably meant to call it also with a string.

[ricardograca]

I’m pretty sure this is in no way related to Bookshelf, but is probably due to the fact that on the second call to requestContext.get('requestId') you’re indeed in a different context because:

1. You’re not returning the Promise created in getSomethingInDB()
2. There’s no mention of how the getSomethingInDB() is being used