Can find be executed immediately after a collection is populated? about forerunnerdb HOT 3 CLOSED

Hey ya,

Does your array in setData() have any data in it? When you say weird, you talking about the __fdbOp and cursor objects returned as properties of the array?

Those are expected. Are they causing you any issues?

from forerunnerdb.

Yes, setData has an array of 93 items in it.
According to the docs, collection.find({}) should return all docs or an empty array if there are none. So why does it return a cursor? And it doesn't appear the cursor that it returns is similar to MongoDb's cursor. I'm not complaining but trying to understand how it works.

from forerunnerdb.

No worries, happy to explain!

So the array returned is augmented with some extra properties. Technically the array itself is still empty if no items are returned since the properties are named rather than numbered (although perhaps we should mark them as non-iteratable - browser support issues with that maybe?).

The $cursor is definitely not something that relates to MongoDB in anyway and will probably change - it's all internal stuff that is useful for various bits and pieces such as integrating between collections, views etc with regards to paging large data-sets.

The fdbOp stuff is data returned about the operation that was performed. This is very useful for performance tuning / indexes and whatnot. The main reason these are exposed however is that the new chrome extension will start to make use of internal metrics as it's GUI gets more functionality. The chrome extension is already quite useful for taking a quick look at the browser's ForerunnerDB instance but it will get better and better as I add more to it.

from forerunnerdb.