Hey Bry4n, this is behaviour is definately by design. In your examples, results is the retrieved value. Since Node.js is asynchronous,the synchronous style of "do something, wait, then assign the value to my variable" won't work here. Checkout the README; what you probably want is

examples.insert({ name: "Guest" });
examples.find().addCallback(function (result) {
    // do something with result here
});

It takes a while to get used to this style, but trust me, it's really powerful. Your program can be doing other stuff (instead of idly waiting) while waiting on IO.

Thanks for the answer. The reason I asked for solution because I am using visionmedia's express (node.js web framework)

I tried this in express:

get("/set/:name", function() {
    examples.insert({ name: this.param("name") })
}); // works perfectly

get("/get/:name", function() {
   examples.find().addCallback(function (result) {
        return result;
   });
}); // doesn't work because express can't read the value from return

Unfortunately, the browser is hanging and asking for the return of value.

Any thought?

I don't know that framework, but it should provide an asynchronous way to complete the request. Glancing at it's docs, it looks like it uses 'this'. It'd probably be something like:
get("/get/:name", function() {
var that = this;
examples.find().addCallback(function (result) {
that.finish(result);
});
});
Or something like that. If there isn't an async option instead of return, basically the whole framework is missing the point of node.js.