<    April 2017    >
Su Mo Tu We Th Fr Sa  
                   1  
 2  3  4  5  6  7  8  
 9 10 11 12 13 14 15  
16 17 18 19 20 21 22  
23 24 25 26 27 28 29  
30
00:18 kyuwonchoi joined
00:32 kexmex joined
00:36 castlelore joined
01:02 compeman_ joined
01:28 <malwar3hun73r> Derick, are you around?
01:29 <malwar3hun73r> I'm wanting to compile from source so as to change the default BSON size from 16 to 32
01:29 <malwar3hun73r> I've been all around on this subject, but I've never been able to get it to work
01:37 hfp_work joined
01:38 compeman_ joined
01:54 DyanneNova joined
02:16 jrajav joined
02:16 <jrajav> hi!
02:17 <jrajav> If I have a query, what's the best way to get all the elements out of it after a first N elements?
02:17 <jrajav> I tried .skip() and it doesn't work as I expected
02:35 codeamend joined
04:03 SkyRocknRoll joined
04:18 joshontheweb joined
04:24 SkyRocknRoll joined
05:41 compeman_ joined
05:44 jri joined
05:48 jri_ joined
05:51 lpin joined
05:59 jri_ joined
05:59 rendar joined
05:59 joshontheweb joined
06:11 compeman_ joined
06:18 jri joined
06:26 jri joined
06:41 jri joined
07:18 jri_ joined
07:21 preludedrew joined
07:23 jri joined
07:24 Mia joined
07:24 Mia joined
07:29 jri joined
07:43 compeman_ joined
07:47 _jd joined
08:26 castlelore joined
08:26 castlelore joined
08:40 compema__ joined
09:41 Axy joined
09:41 Axy joined
09:46 Mia joined
09:46 Mia joined
09:48 Axy joined
09:48 Axy joined
09:51 Frostman joined
10:32 re1 joined
10:38 kexmex joined
11:27 Folkol joined
11:34 compeman_ joined
11:56 yeitijem joined
12:00 compeman_ joined
12:20 Guest26164 joined
12:54 Folkol joined
12:55 swordbeta joined
12:59 kexmex joined
13:35 bytee joined
13:36 bytee joined
13:47 chevz joined
13:52 chevz joined
14:00 geoffb joined
14:10 StephenLynx joined
14:20 felixjet joined
14:30 jrajav joined
14:30 <jrajav> Hi! is using .skip() on a query the right way to drop the first N elements off of it before performing an update?
14:30 <jrajav> Because I'm doing that and it's not working, at all
14:49 chevz joined
15:02 kexmex joined
15:20 Folkol joined
15:22 itaipu joined
15:47 compeman_ joined
16:03 compeman_ joined
16:19 orbyt_ joined
16:30 silenced joined
16:32 compeman joined
16:38 kexmex joined
16:43 timg__ joined
16:53 re1 joined
16:59 okapi joined
17:03 compeman joined
17:05 svm_invictvs joined
17:08 Stephen joined
17:11 Siegfried joined
17:13 tildes joined
17:15 silenced joined
17:19 kyuwonchoi joined
17:30 itaipu joined
17:33 compeman joined
17:40 armyriad joined
17:43 Stephen joined
17:45 timg__ joined
18:02 compeman joined
18:11 compeman joined
18:13 compeman joined
18:20 compeman joined
18:22 Siegfried joined
18:28 rendar joined
18:28 rendar joined
18:58 felixjet joined
18:59 coudenysj joined
19:32 okapi joined
19:32 kexmex joined
19:33 itaipu joined
19:37 timg__ joined
19:40 compeman_ joined
19:48 InfoTest joined
19:53 m1dnight_ joined
19:59 silenced joined
20:01 kyuwonchoi joined
20:02 kyuwonchoi joined
20:08 re1_ joined
20:18 orbyt_ joined
20:46 gentunian joined
20:54 Necromantic joined
20:56 jaequery joined
21:02 itaipu joined
21:16 <apoc> so with mongodump --forceTableScan does it still use the _id index?
21:17 <apoc> I did the mistake and use a custom random _id (md5sums) and now that causes huge issues
21:19 <apoc> is there a way to prevent the seeking in this scenario? I thought forceTableScan is supposed to do that
21:26 Siegfried joined
21:33 compeman joined
21:52 compeman_ joined
22:09 chevz joined
22:12 Lujeni joined
22:51 compeman joined
23:03 <joannac> apoc: yes, scans the data directly and doesn't use the _id index.
23:07 <apoc> strange, its still incredibly slow and I tought its the _id
23:08 <apoc> disk is mostly seeking around
23:34 Mia joined
23:34 Mia joined
23:46 NoOutlet joined
23:49 chevz joined
23:58 gentunian joined