Log file Viewer

[05:00:11] <NoOutlet> Whew. Just got acquainted with mtools. Pretty nice set of tools there.

[07:48:43] <iksik> hmm, is it possible to find out if document's object field has at least one property != null?

[08:39:20] <oznt> hi everyone, is there a way to incorporate a javascript snippet in my c code for mongodb? I found that I can use "mongoc_collection_command_simple" to execute commands, but I can see any output if the javascript snippet includes "printjson"

[10:04:21] <kdabrowski> Hello guys. Happy day to you all. I am here to ask you about one thing I am wondering today regarding MongoDB and its quota for number of files.

[10:05:28] <kdabrowski> I have a ReplicaSet of two nodes: primary and secondary. I have quota enabled (default: 8) I have 10 allocated files for database X on Primary node and more than 20 on Secondary node in the same ReplicaSet. Why? :)

[10:14:53] <kdabrowski> Anyone? :)

[10:56:53] <reliability> hi

[13:05:03] <reliability> If I have a document collection where each document contains a (potentially large) array containing subdocuments and I need to efficiently query the subdocuments, how should I structure my documents?

[16:25:22] <TallGuy55_> new user here, Hello World

[16:30:50] <Derick> hey TallGuy55_

[16:31:01] <TallGuy55_> Hi

[17:14:54] <mst1228> i'm using Mongo with Node and writing a REST API, is it bad practice to use the ObjectId Mongo assigns my documents as resource id in my API, or should I be creating my own, alternative id field for API sake?

[17:21:42] <GothAlice> mst1228: Depends on how much information you are willing to leak from your API.

[17:22:09] <GothAlice> ObjectIDs include the process ID of the application process that created the ID, an auto-increment number for that machine, and the timestamp of that record's creation.

[17:23:05] <mst1228> GothAlice: thanks you very much

[17:23:22] <GothAlice> For my own datasets this level of information "leakage" isn't a problem; we supply the creation time anyway. And using a freshly created ID to attempt to predict the *next* ID to be generated poses little risk as we have access controls preventing casual shenanigans.

[17:27:54] <GothAlice> Argh, my brain on net/splits.

[18:24:00] <fn_steve> i have a quick question about shard keys.

[18:24:23] <fn_steve> in reference to: http://docs.mongodb.org/manual/reference/limits/#Shard-Key-Value-in-a-Document-is-Immutable

[18:24:50] <fn_steve> if i were to choose a compounded shard key, as an example, of { _id: 1, email: 1 }

[18:25:03] <fn_steve> does that mean i will never be able to change the e-mail address on that document?

[19:07:48] <GothAlice> I've heard of tight loops, but this one is getting ridiculous.

[22:00:31] <Peiniger> trying to find a way to compare a field to another field that resides one level deeper in the document. What im trying isnt working…anyone have a better idea? db.organizations.find( { $where: "this.meta.enabledUsers > this.users" } );

[22:02:02] <Peiniger> one of the hangups for me is that this.meta.enabledUsers doesnt exist in all documents

[22:09:16] <kali> Peiniger: beware, $where is an absolute performance killer

[22:09:44] <Peiniger> kali, thanks

[22:10:47] <kali> Peiniger: you may achieve an equivalent query with the aggregation framework, but from the look of it, you'll need to alter your document model to make this fast