You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 23, 2020. It is now read-only.
The callback should always be last. "opt" should come before callback.
You can use arguments.length to permit people to skip passing opt.
The "only" and "except" mechanisms depend on indexOf in a way that will
do the wrong thing if a collection name happens to be a substring of an
unrelated collection's name. That would need to be fixed.
Closing the stream is a bc break, but since we're still in the 0.x
series, that's OK. We'll need to document this change in the README and in
its changelog section, and we'll need to bump the minor version number (not
just the patchlevel).
It sounds like you are not using this to pipe standard input and output;
you're writing to sockets or other blocking things. The code works for you
because node is willing to buffer as many calls to write() as you want, but
it's certainly going to be a RAM issue at some point. We should think about
waiting for "drain" events if write() returns false, indicating that
buffering is taking place.
(The reason item number 4 didn't come up for me is that standard output is
actually blocking in node. Weird but true.)
On Mon, Jun 1, 2015 at 10:27 AM, Tom Boutell tom@punkave.com wrote:
Hmm, this looks good... a few concerns.
The callback should always be last. "opt" should come before callback.
You can use arguments.length to permit people to skip passing opt.
The "only" and "except" mechanisms depend on indexOf in a way that will
do the wrong thing if a collection name happens to be a substring of an
unrelated collection's name. That would need to be fixed.
Closing the stream is a bc break, but since we're still in the 0.x
series, that's OK. We'll need to document this change in the README and in
its changelog section, and we'll need to bump the minor version number (not
just the patchlevel).
It sounds like you are not using this to pipe standard input and
output; you're writing to sockets or other blocking things. The code works
for you because node is willing to buffer as many calls to write() as you
want, but it's certainly going to be a RAM issue at some point. We should
think about waiting for "drain" events if write() returns false, indicating
that buffering is taking place.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Call callback when operations are done, closes db, and add only, exept support
My use case is that the db I am dumping from has 5 collections, and 2 of them are big and unneeded.