Timur Kristóf comments

Results 171 comments of


                                            Timur Kristóf

Support non-zero-terminated UTF-16 strings in node-lmdb

@hanweifish Please provide the exact steps to reproduce this problem. You get that error when you try to read a UTF-16 string and it's not zero terminated, but `goToFirst` does...

Support non-zero-terminated UTF-16 strings in node-lmdb

@hanweifish In that case the data is not a valid zero-terminated UTF-16 string.

Support non-zero-terminated UTF-16 strings in node-lmdb

@hanweifish Explanation: in the beginnings it was unclear whether V8 requires zero termination on its strings or not, so I added the terminating zero just in case. These days V8...

Support non-zero-terminated UTF-16 strings in node-lmdb

Until this is solved, I can give you a temporary solution: ```js var cursor = new lmdb.Cursor(txn, dbi, { keyIsBuffer: true }); for (var key = cursor.goToFirst(); key !== null;...

Support non-zero-terminated UTF-16 strings in node-lmdb

@da77a Yep, that's exactly what I suggested. :)

Support non-zero-terminated UTF-16 strings in node-lmdb

On the longer run, though, I will add an option that will allow the use of non zero terminated strings as well.

Support non-zero-terminated UTF-16 strings in node-lmdb

@hanweifish Generally, you are expected to know what encoding you store your strings with.

Support non-zero-terminated UTF-16 strings in node-lmdb

Let's keep this issue open for now, to keep track of non-zero-terminated strings support.

Support non-zero-terminated UTF-16 strings in node-lmdb

@matthewaveryusa I know I could do whatever I want, but I don't want to give a hard time to my users, is all.

Support for mdb_cursor_put()

@degifted Sure, can you give me an example use case?