[01:34:24] <owen1> is that the right way to connect to a replica set? MongoClient.connect('mongodb://1.foo.com:27017,2.foo.com:27017,1.foo.com:27017/test', connected)
[01:34:55] <owen1> (and it will be fine even if not all dbs are up?)
[01:52:59] <LesTR> that's depend on client library
[01:54:58] <LesTR> for many library you save when one of host from you list are on live
[01:55:38] <LesTR> and other comunication will be based on active nodes in rs
[01:56:17] <LesTR> so you need only one alive host from your list for connect
[01:57:32] <LesTR> but this depnend on client lib : )
[02:14:35] <owen1> LesTR: the official 10gen client for node
[02:15:17] <owen1> LesTR: i did some tests (like killing one of the mongod process) and everything seems to be fin
[17:33:36] <steverabouin> hello -- I have a huge problem with mongo+php and simply can't figure it out. I'm running a query on a large collection (153176597 items) -- the first query works fine using the index, returns result less than 1 second, the next query seems to never want to stop. Running these same queries in the shell return results instantly. I am at a loss on how to resolve this problem. Any pointers?
[17:34:45] <steverabouin> interestingly enough, if I close/reopen a mongo connection before the second query, it responds instantly
[19:54:44] <w3pm> are there general guidelines for when its a good idea to use separate collections/
[19:55:27] <w3pm> ie is there some reason i shouldnt just throw everything into the same collection and tag docs with what they are (with some 'type' property)
[20:04:20] <markstory> When using the aggregation framework is there a way to do timezone conversions? as $year, $month, $dayOfMonth etc all create the year/month/day in UTC
[20:04:43] <markstory> which creates subtly different data than grouping by a user timezone.
[20:57:07] <wavesounds> Is this ok in an update query? Syntax correct? $push: {'voters': {['id':Session.get("ownerId"), 'name':Session.get("name")]} },