Question regarding passing additional args about nano-sql HOT 5 CLOSED

What's the relationship to the extra data? Is it tied in anyway to the data being pulled from the database?

from nano-sql.

No. It's strictly ancillary data that needs to be tweaked based on the nSQL data. Just wondered if there might be a need for some pass-through data as an option. The main reason is because once you enter the promises for nSQL nothing outside the scope of nSQL is available even though it might be scoped inside a function that contains the nSQL calls.

from nano-sql.

There's an undocumented property on the nSQL variable that can hold arbitrary data:

nSQL().data = {something:"here"};
console.log(nSQL().data.something): // <- "here"

The variable isn't used by the lib at all, so it's up to you to initialize it and use it how ever.

Beyond that, since the data isn't related to the nSQL data it kind of makes sense to manage that outside of the nSQL store, just my two cents.

from nano-sql.

Also, scope usually allows you to access parent scoped variables inside the promise.

var globalVar = "yo".
nSQL("table").query("select").exec().then(function(rows, db) {
   console.log(globalVar) // <- "yo"
});

There's a really good article on Medium that covers JS closures, might make this make more sense.

from nano-sql.

ok, thanks a bunch

from nano-sql.