David Burles
David Burles
Hey @n1ru4l do you have much of an idea how you might want this to function? I could take a look at it.
I'd also like to see pre-built ARM binaries.
Hey thanks, good suggestions, I'll work on them for the next release :)
Yeah that's a bit tricky, I'm not entirely sure of the potential use cases (we haven't had any issues crop up relating to looking up null collections so far)
Potentially we could allow extra naming feature for both null and named collections, this may make handling multiple connections a lot more intuitive
Rather than passing in the connection, we can instead reference the name
``` js Foo1 = new Mongo.Collection('foo', { ref: 'foo1' }); Foo2 = new Mongo.Collection('foo', { ref: 'foo2', connection: ... }); // if a 'ref' is passed in, we use that...
I think in that case, if you define null collections without a reference, we just ignore them
I don't think that'd be possible due to the name clash
Do you mean another connection?