nstore #3
Open
nstore #3
Conversation
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
noithing important, just a fix to make nstore work with newer versions of node in your examples. (The file you included (nstore.js) will not work on node >0.4)
Currently nstore (0.3.0) and all predecessors are broken with node 0.4.3 (the problem resides in nStores buffer handling, and I already wrote a pull request to Tim Caswell, the author of nStore that fixes the problem).
If you like, you can also wait, until he implements a fix, so you don't rely on my patched version.
Btw. is there a way, to get a word/term frequency count of the words in a certain document or do you know some library that can extract that information easily?
Best regards
Gregor