[03:02:21] <sifat> Hi all - I have a strange issue. When I run this code: https://dpaste.de/kLNz the updates work fine. But the moment I uncomment the next $set (https://dpaste.de/1JjO), the Name column fails to update. How could this be?
[03:30:17] <sifat> fixed this by using only 1 $set operator
[21:57:51] <simonv3> Hey all, I’m wondering about an architecture decision and what the best route for it would be. I’m working on a project that has a bunch of Users and Guides, and for each user we calculate a compatibility score for each guide. At the moment we calculate that on each request (it’s a Rails app using mongoid FWIW), but while up to recently that was
[21:57:52] <simonv3> sustainable things have started timing out and blocking here. So I figure that a form of “caching” the compatibility score is the best way to go ahead on this so that it only calculates the score every day or so (this can be optimized further down the line, every day is fine for now). But I’m wondering how to architect this. What makes most sense to me
[21:57:52] <simonv3> is to have a relationship on the User that stores each-pre-calculated guide’s score. I think embedding it makes sense?
[21:58:37] <simonv3> (this might be where my experience with relational dbs is influencing my thought process too much though)
[23:18:08] <Trinity> hi, i'm trying to use authentication in mongo and so far I can log in using my credentials when authentication is turned off
[23:18:17] <Trinity> but when it is on, i get the following errors
[23:18:47] <Trinity> user@hostname:~$ mongo -u user -p somePass --authenticationDatabase admin