Log file Viewer

[01:16:35] <jessepollak> anyone here have a second to answer a concept question related to mongodb?

[02:51:33] <azbyin> hi all.. How would I search a collection(call it coll) for all documents where the username property begins with a certain string?

[02:57:08] <dangayle> azbyin: regex

[02:57:15] <dangayle> $regex

[02:58:19] <azbyin> but i heard regex doesn;t use the index or something

[03:00:04] <dangayle> If you're searching at the beginning of a string it does

[03:00:42] <dangayle> ^abc will use the index on a

[03:03:58] <dangayle> "$regex uses indexes only when the regular expression has an anchor for the beginning (i.e. ^) of a string. Additionally, while /^a/, /^a.*/, and /^a.*$/ are equivalent, they have different performance characteristics. All of these expressions use an index if an appropriate index exists; however, /^a.*/, and /^a.*$/ are slower. /^a/ can stop scanning after matching the prefix."

[03:04:02] <dangayle> http://docs.mongodb.org/manual/reference/operators/#_S_regex

[03:04:13] <azbyin> cool.. so i can do db.coll.find({username:"^john"}) ?

[03:05:13] <dangayle> yeah, if you aren't combining it with other operators

[03:15:14] <LesTR> dangayle: have you experience with regexp in production? On real dataset.

[03:15:25] <LesTR> It's only question

[03:16:11] <dangayle> LesTR: I've never had large enough datasets to work with in production

[03:16:16] <dangayle> sorry

[03:16:30] <LesTR> ok, thx for response

[06:31:41] <matbee> out of curiousity, does anyone know how i could get a single document where its date property is greater than a specified date-- and one of its properties contains a number, and I want to only choose the document where that property is the smallest

[06:32:21] <matbee> so like, { dateProperty: 07/07/190, numberProperty: 5 }, { dateProperty: 07/07/1950, numberProperty: 3 }, { dateProperty: 07/07/2000, numberProperty: 1 }

[06:32:24] <matbee> it would choose the last one

[06:33:01] <matbee> so like, { dateProperty: 07/07/190, numberProperty: 5 }, { dateProperty: 07/07/1950, numberProperty: 3 }, { dateProperty: 07/07/2000, numberProperty: 1 }

[06:33:43] <matbee> or would I only be able to filter by date and sort?

[06:34:21] <matbee> well that was weird-- I somehow pasted.

[07:35:03] <synchrone> Hi all! I was wondering, what happens if in my .NET application I try to use MongoDBFileStream after IDisposable RequestStartResult object was disposed ?

[11:04:13] <calum_> I thought 10gen's mongo course was excellent did anyone here do it?

[11:05:55] <ron> I had a nasty experience with a 10gen representative, doubt I'll try a course.

[11:07:43] <calum_> That is a shame. I was interested in mongo and it gave me a really good running start at it. It had its issues but as it was free you cant complain. THe only thing it really lacked on was real life situations for collection 'schema' design

[11:08:32] <calum_> It is hard to workout what is the best way to approach a situation. But there again that is development through and through

[11:09:45] <ron> well, there's no 'best way' there. there can be several solutions to a single problem. besides, I believe schema building is blown out of proportion. it really isn't all that difficult.

[11:10:43] <calum_> Well that was sort of the conclusion I came to. It is just hard as with relational there are so many 'Best

[11:10:47] <calum_> Practices'

[11:11:07] <calum_> Hard to accept that is. lol

[11:14:09] <calum_> The only major issue I see with mongo is that the key names take up space in each document. This leads you towards meaningless short key names to compensate. This seems to lead to a situation where you need to add complexity to keep data small and fast. I am sure they will sort this in a release with an alias map or something similar but it just seems to go against logic at the moment.

[12:19:06] <wereHamster> calum_: ideally your ODM would allow you to use long names and translate them to short ones when saving

[12:49:44] <calum_> wereHamster: That would be an ideal situation. I might develop a mapping / aliasing system and see where it takes me. :)

[12:50:29] <calum_> wereHamster: I do think this will end up being built into mongo though.

[13:02:49] <wereHamster> nope, it don't need to. It's entirely up to the driver/odm to do that

[13:18:43] <joe_p> when enabling sharding for a database how is the shard assigned. i created 6 databases and all were assigned the same primary shard

[13:38:37] <wereHamster> maybe there is not enough data to split

[14:55:25] <bartzy> Hello

[14:55:47] <bartzy> an integer flag (0,1,2 for example) is bigger than a string '0', '1', '2' ?

[15:18:50] <yakubori> hello

[15:20:00] <yakubori> if anyone here is familiar with the Perl driver, is it necessary to use MongoDB::MongoClient explicitly, or should one be able to get away with use MongoDB only?

[15:23:15] <yakubori> nm -- i must have squished something with perlbrew. re-ran cpan MongoDB and all is well :P

[15:24:37] <kali> yakubori: http://blog.mongodb.org/post/36666163412/introducing-mongoclient i'm not sure about the perl driver, but you may want to read that :)

[15:30:30] <yakubori> i just didn't have the Client module on the system for some reason, kali. so, 'use MongoDB; my $client = MongoDB::MongoClient->new;' was failing. i'm guessing it had something to do with messing with perlbrew *after* i had first installed the driver… (shrug)

[15:31:09] <yakubori> interesting post tho, thanks :)