[09:17:12] <synthmeat> is there an option to hint mongo that an array is fixed size?
[11:04:00] <GothAlice> synthmeat: https://docs.mongodb.com/manual/reference/operator/update/slice/#up._S_slice ← note that this is a modifier to $push'ing a new value into an array. Arrays aren't actually fixed-size in any meaningful way.
[11:04:46] <synthmeat> GothAlice: yeah, i meant it as a performance hint maybe, i know about keeping it same size
[13:17:33] <sfs> i can see only ppc64le in SConstruct, but i'm not sure whether just changing to ppc64 is enough or there are some endianness issues
[13:18:14] <GothAlice> sfs: It’s a network service. There are endian issues.
[13:20:05] <GothAlice> Also data portability issues, given MongoDB’s extensive use of memory mapped files. E.g. data files need to be portable between architectures.
[14:11:51] <synthmeat> how do i specify read concern as majority on a (node.js) .find()?
[14:38:09] <s10g> Does mongodb have default env vars it can consult for connection info, like postgres' PGUSER, PGHOST etc?
[14:54:27] <synthmeat> would be a news to me if it did
[15:44:46] <GothAlice> s10g: The command-line tools have a few defaults. ‘man mongo’ (or the other tools such as mongodump) and they should be documented.
[15:45:23] <GothAlice> E.g. defaulting to localhost. (mongo xyzzy <- attach to that db on localhost, default port)
[16:53:39] <sfs> GothAlice: it looks like sparc and s390x (which are both big-endian) are supported
[18:03:47] <synthmeat> so, i have no clue how to use readConcern and writeConcern majority with node.js driver