Log file Viewer

[00:08:58] <daidoji> mikeylikesit: depends on the hardware/sharding/replication setup/application profile you've got going

[00:09:11] <daidoji> I think the canonical advice is "denormalize everything"

[00:09:31] <daidoji> followed closely by "store keys in documents and iterate over keys"

[00:09:38] <daidoji> followed by "join in the application"

[00:09:55] <daidoji> although that last one is advice that could really apply to the first two as well

[00:10:45] <daidoji> (I'm no expert but I've been reading up on it currently cause I've been doing the same thing myself recently unfortunately)

[00:13:38] <mikeylikesit> Join in the application is what I have been seeing mostly as well.

[00:14:25] <daidoji> mikeylikesit: yeah, although depending on how much the cost of disk space irks you, the denormalize thing seems like a better idea 90% of the time

[00:14:46] <daidoji> and your use case obviously

[00:16:34] <mikeylikesit> daidoji: yeah, I think I like the sounds of the denormalize thing, and honestly, my use case probably doesn't warrant me worrying too much about performance, I would however like to figure out the "blessed way"

[00:21:17] <daidoji> mikeylikesit: for key/value stores denormalize is probably as close to that as you'll get

[00:21:25] <daidoji> not to mention it'll make your app way easier to code

[00:22:47] <mikeylikesit> yea, the more I am reading the more enticing denormalization looks

[01:09:46] <joshua> mongo mongo mongo. can't get enough mongo

[01:12:06] <jamesd> are you cuckoo for mongo mongo

[03:38:36] <windsurf_> I want to update and return the record I updated. Should I make an upsert THEN findOne or is there a conventional way of combining these?

[03:39:52] <cheeser> http://docs.mongodb.org/manual/reference/method/db.collection.findAndModify/ upsert=true

[03:42:31] <windsurf_> cheeser: thanks!

[05:22:07] <LouisT> is it possible to allow non-admin users to issue serverStatus on a db besides "admin"?

[05:25:09] <joannac> serverStatus isn't database specific