[00:08:19] <colwem> Ok, so I have an app that uses mongodb on the backend. The app is complicated, I didn't write it and I don't want to touch it. But I'm writing something that interacts with it's api. So what I'd like to do is fool this app into using a test db rather than the dev db it's currently connected to. Is there any way to do that? Like can tell mongo to "alias" on db to another?
[00:10:10] <colwem> Cause you know I'd rather not nuke the dev db every time I run the tests.
[00:16:53] <Boomtime> @colwem: that app connects to a specific destination, it has an address that it is connecting to, you don't need mongodb to intercept that - networks are literally designed to route and re-route wherever you want
[00:17:33] <Boomtime> to be clear: use a NAT router to send it to whatever database you want
[00:24:25] <colwem> Ok... unfortunately as of right now I have no idea how that works or how to do that. Networking is something I know so little about. But if that's how it has to be done then alright.
[00:26:08] <Boomtime> well, it's either that or find the one line in the app where it specifies what to connect to and change it
[00:26:28] <Boomtime> if the app is written even semi-decently, it will have a single location where the connection-string is specified
[00:27:19] <Boomtime> decent apps actually export the connection-string to a configuration file or some such
[00:27:23] <colwem> Boomtime: oh it does, that's not so hard, it's in a config file.
[00:29:08] <colwem> Boomtime: right well that's why I thought maybe mongodb would do that for me.
[00:29:34] <Boomtime> what do you expect mongod to do?
[00:29:47] <Boomtime> the app would still be talking to a different database right?
[00:30:00] <colwem> But yeah I just realized that I can just run two instances of the app with different config files and I'm good. Obvious solution that i completely overlooked.
[00:30:03] <Boomtime> this has nothing to do with mongodb, it has to do with different _data_
[00:30:24] <Boomtime> right, if you can run two instances, absolutely do that, all neat and tidy
[00:31:06] <colwem> Yeah, so... sorry about wasting your time.
[00:31:25] <Boomtime> is all good, talking it through is often what is needed
[08:06:09] <mylord> how do you find where subdoc’s properties/subsubdocs number > x?
[12:39:34] <escamoteur> [14:24] #mongodb: *** topic is 3.2.5, 3.0.11, 2.6.12 -- http://mongodb.org/ http://jira.mongodb.org/ http://groups.google.com/group/mongodb-user/ http://irclogger.com/.mongodb -- Can't talk? Register your nick: /msg nickserv help register
[12:39:35] <escamoteur> [14:24] #mongodb: *** set by GothAlice!~amcgregor@unaffiliated/gothalice on Fri Apr 22 19:23:07 2016
[12:39:35] <escamoteur> [14:24] #mongodb: *** channel created at Tue Jan 27 15:20:06 2009
[12:39:35] <escamoteur> [14:26] #mongodb: <escamoteur> Hi, just starting out with mongo and run into a problem. Could anybody have alook at http://stackoverflow.com/questions/36809891/mongodb-c-sharp-driver-v2-exception-in-findasync-after-updating-nested-collecti
[12:40:20] <escamoteur> Sorry just made a misstake with my IRC client
[12:42:10] <escamoteur> I just started with mongo and ran into this problem and I'm completely lost http://stackoverflow.com/questions/36809891/mongodb-c-sharp-driver-v2-exception-in-findasync-after-updating-nested-collecti