-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nodedb should handle undefined and Buffer as input #12
Comments
This completes the previous issue, as I proposed a debug for fetching binary data (ie. buffers) and this proposes a feature to store it easily. |
Yes, I'm already using your patch as stated in a comment. Happy this is of help to you ;-). |
I'm a little sad to see users taking time to come up with issues and their related patches are not welcome enough here to get even an answer. Is this project stil maintained or is it abandonned? |
@even First of all thanks for the patch. Could you fork the project and make a pull request so credit is given where its due? |
I would do so if I have to but I'll need to install git and (re)figure out how it works because I haven't used git in decades... I'm a mercurial guy. Yeah I know, I've fallen to the dark side. I'm not really looking for popularity, I'd rather let you push the patch with your account and be done with it. If it's fine with you. |
I wouldn't call mercurial the dark side, I like it a lot :) But still GIT is my all-time-fav ;) Ok I'll work on patching this |
Great ! And thanks for the quick answer. It would be awesome if you could do something about bug #11 too because it's related. One is needed to insert buffers and the other to retrieve them without corruption... |
I believe nodedb should support Buffer as a standard input type because they are the (only ?) "correct" way to handle binary in nodejs. I also believe undefined is quite like NULL in a database and added support for this too because this looks sensitive.
I wrote the following patch to do just that (sorry I'm not a git user and thus won't make a pull request directly on github) :
This patch was written on the released file but it should work on the newer one without much adaptation.
Thanks a lot for considering this little addition to your base code.
The text was updated successfully, but these errors were encountered: