Inconsistent usage of this.database about doqmentdb

[JanneSalo]

Hmm, could this maybe be fixed simply by adding a new property in the DoQmentDB object: this.dbName, initializing it in the constructor and then passing this.dbName to Collection constructor?

[a8m]

Thanks @JanneSalo
Updated version v0.2.4, fix this bug and also added operations supporting, see: README
I'm just curious why you don't using collection simply like that ?

var db = new DoQmentDB(...)
  , users = db.use('users');

users.find({})
  .then(console.log)

[JanneSalo]

Thanks! I just tested this and the issue indeed seems to be fixed.

There's a reason I'm getting the collections in such a peculiar way. It all comes down to working around DocumentDB limitations, really. I work on a project where the 10GB cap on collection might become an issue, so we've had to split some data that logically belongs in one collection into several collections. I wrote a little wrapper function to query across all collections at once, but in order to do that, I first need to know which collections exist in the database as simply getting collection manager for each possible collection (there aren't that many, but still) isn't an option because doing a find() on a collection that doesn't exist causes the collection to be created and that's where we run into another limitation of DocumentDB: only 3 collections per CU are allowed. That's why I need to know what to query before I query. :)