[02:43:42] <Gavilan2> Hi! How bad an idea is to use a single "collection" for all my apps documents? When will that stop performing well?
[03:49:46] <timeturner> qq, is it commonplace to give confirmation links that look like: http://mydomain.com/confirm/238#*asfdDF OR http://mydomain.com/confirm/?user=test@example.com&code=238#*asfdDF ?
[03:50:10] <timeturner> not sure where else to ask this question :/
[03:55:04] <Gavilan2> Hi! How bad an idea is to use a single "collection" for all my apps documents? When will that stop performing well?
[03:56:11] <timeturner> single collection? not good
[07:20:03] <Dr{Wh0}> Can i exclude a database from replication?
[08:19:56] <dotblank3> I have a question about queries and Date indexes
[08:20:14] <dotblank3> How do I query for the first closest date
[08:26:30] <kali> dotblank3: if you want the first after, db.foo.find({ timestamp: { $gte : .... } }).sort({timestamp: 1}).limit(1)
[08:26:56] <kali> dotblank3: if you want the first before, same with $lte and reverse order
[08:27:27] <kali> dotblank3: and if you want the closest whatever the direction is, you need to do both request and find out which one is better application-side
[08:28:54] <dotblank3> Why do I need to use sort? If I have an index on Date can I use the natural order to quickly return entries that have been added sequentially
[08:30:21] <kali> dotblank3: if you never delete or update records in the collection, that could work. but as you have an index on the date, the sort will just do the right thing
[08:30:55] <kali> dotblank3: i prefer not to rely on physical layout when i'm expressing a "logical" thing
[08:31:29] <dotblank3> well, this is more or less a log file and a capped collection
[08:31:50] <dotblank3> soI will always now the natural order will be in sequential ascending date order
[08:33:40] <kali> i have a similar situation in my infrastructure, and the insertion order is often slightly off
[08:33:48] <dotblank3> Is the penalty large moving to sorted indexed result from a natural order sort
[08:33:50] <kali> because various soure will take more or less time to write
[08:34:39] <kali> dotblank3: nope, it will realy be marginal in this case, so i recommend strongly putting the sort on timestamp :)
[08:35:03] <dotblank3> Awesome, thanks for your help!
[12:54:51] <ron> say we finally have a semi-production environment, and we notice a load that's... a bit more than we expected, how would we go about debugging the situation?
[13:43:26] <gigo1980> does have anyone tried the mongodb hadoop connector ?
[13:44:10] <gigo1980> because i have an bootlneck in my map reduce in mongodb / so only one core for the v8 engine is available
[14:36:41] <defaultro> good morning folks, what tcp port does MongoDB use? And how do I add username/password to access the collection?
[14:38:00] <Derick> and http://es.wiki.mongodb.org/display/DOCS/Security+and+Authentication#SecurityandAuthentication-RunninginSecureMode%28with\author\keyFile%29
[14:58:45] <defaultro> use mydb then db.auth('someuser','somepass') then db.addUser('someuser','somepass') then i type exit to go back to console. I ran mongo localhost/mydb
[14:59:15] <defaultro> i ran show tables and I didn't see "you're not authed"
[15:18:40] <hillct> Good afternoon all. I'm trying to understand ranged request pagination where the initial request can be more or less arbitrary, as opposed to a simple timeline type ranged pagination
[15:19:41] <hillct> To accomplish this, I'm looking at the Twitter style of pagination which seems to be to create a hash representing the initial search query plus the ranged offset value
[15:33:24] <jpfarias> I upgraded my shard server to 2.2.0 and now I am having some problems, is it ok if I downgrade to 2.0.7?
[15:41:39] <jpfarias> this is the error I am getting: http://pastie.org/4690770
[15:41:46] <jpfarias> I have no idea why that is happening
[15:55:09] <defaultro> so happy, I am now able to save data to mongodb from my leaflet and openstreetmaps :)
[16:45:25] <hillct> When you sort by _id you get an order by _id creation time which is handy, but is there a way to test that timestamp in a query? I tested the query {$id.generation_time:{$lt: mongoIdTimestamp } } but found it failed to survive the Node.js module compilation
[16:47:05] <hillct> Is there a way to implement a query that evaluates the timestamp embedded within an ObjectID?
[16:51:07] <hillct> BurtyB: the default ID objects have a timestamp embedded in the first 4 bits
[17:38:03] <hillct> There's actually docs describing most of what I need to be able to do: http://www.mongodb.org/display/DOCS/Optimizing+Object+IDs but I don't see how to utilize _id or $id timestamp values in queries, for example $id.getTimeStamp(): {$lt: mongoID.getTimestamp()}
[17:38:32] <hillct> however that syntax isn't getting it done
[17:51:13] <hackeron> hey, if I have a recording collection that references a camera and a camera collection that references zone - is there anyway to query something like Recording.where(:camera.zone => my_zone)?
[18:20:35] <hillct> In reviewing these patches relating to timestamp extraction from objectIDs, I can't discern how to perform comparison operations on the timestamp portion of an _id from within a query, but it seems like that functionality was added two years back...
[18:24:16] <defaultro> hey folks, is it possible to remove _id?
[18:25:22] <kali> hillct: the timestamp are at the beginning if the _id, so you can just compare them
[18:26:02] <kali> hillct: be aware that it is only at the granularity of a second
[18:26:55] <defaultro> i'm trying to parse the data from javascript but the random id is giving me a hard time
[18:28:48] <hillct> kali: I've been looking at this all afternoon and can't work out how to use the _id timestamp component in a query constraint. Can you give me an idea how that would work? Comparing the first 4 characters, or parsing the first 4 characters as a timestamp doesn't do it. What do they need? Hex decoding?
[18:29:38] <kali> hillct: you need to generate fake objectid
[18:29:52] <kali> hillct: what driver are you using ?
[18:34:01] <hillct> kali: or do you mean to generate a bogus ObjectID, then perform the comparison of ObjectID to ObjectID, rather than extract the date time from the existing objects against which the comparison is being performed
[18:34:03] <kali> hillct: you want to create an objectid with the date you want to use as a comparison
[18:34:22] <kali> hillct: and compare your collection objectid to this one
[18:34:48] <hillct> kali: ok, I guess I was thinking about comparing the raw (exported) date time strings, which is obviously a wrong approach, now that I look at it
[18:35:25] <kali> hillct: you need to compare the actual type stored by mongodb if you want the index to work... hence the "fake" objectid
[18:35:35] <hillct> kali: thanks. Now that it's been pointed out, it of course seems obvious
[18:36:13] <hillct> kali: I'll code it up as you suggest, and I'm pretty sure it'll work...
[20:26:57] <dominik-zogg> i use the MongoDBBundle, and got a problem with the form type document
[20:27:28] <dominik-zogg> have you an idea why no set add method get called in document?
[20:28:35] <jmikola> not offhand; that's all common functionality of the DoctrineType in Symfony -- likely not specific to the bundle
[20:28:44] <dominik-zogg> other data i form get stored form -> doctrine -> mongdb without any problem
[20:29:37] <dominik-zogg> i mean this here: https://github.com/doctrine/DoctrineMongoDBBundle/blob/master/Form/Type/DocumentType.php
[20:30:54] <jmikola> the actual logic is in https://github.com/symfony/symfony/blob/master/src/Symfony/Bridge/Doctrine/Form/Type/DoctrineType.php -- the class you're pasting is just as wrapper for some ODM binding
[20:31:30] <jmikola> i don't see anything specific in the DoctrineType about calling add/set methods, so this is likely not even a DoctrineType issue -- probably a generic Symfony forms question
[20:31:41] <dominik-zogg> i worked with the entity version of this last week, on a other project, without a problem