Supporting UTF - 8

[ZuzooVn]

As we already discussed here: QEWD-Courier/Ripple-Qewd#40

How can setDocument() support UTF 8?

Thanks

[linto17]

Hi, is this fixed?

[ZuzooVn]

@linto17
I created the pull request here: #18

[dileep-ehr]

Hi,

There seems to be a relates issue discussed in the following thread. Though it is about using YottaDB, the problem is very similar to what is reported here.
https://groups.google.com/forum/#!topic/enterprise-web-developer-community/5yXC166Qh78

In one of the replies Rob mentions that he has understood the issue and will be able to explain how to configure QEWD to address this problem. Has this been posted somewhere? If not can somebody post it here for everybody's benefit? Many people seem to be having this problem

[killmenot]

@dileep-ehr I believe Rob wants setDocument/getDocument were not affected by changes in #18 if it's not needed. Let me try to patch solution #18 and add tests and then I will ping Rob

[dileep-ehr]

Thank you. I think it will be a great value addition to QEWD community. regards Dileep V S *Founder* HealtheLife Ventures LLP m: +91 9632888113 a: 106, Innovation Centre, IIIT, Electronics City, Bangalore 560100 w: healthelife.in e: dileep@healthelife.in

…

On Tue, Oct 9, 2018 at 12:02 AM, Alexey Kucherenko ***@***.*** > wrote: @dileep-ehr <https://github.com/dileep-ehr> I believe Rob wants setDocument/getDocument were not affected by changes in #18 <#18> if it's not needed. Let me try to patch solution #18 <#18> and add tests and then I will ping Rob — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVVRXAwDa_h_QYN1Z2M86BxBV5wMOevsks5ui5pbgaJpZM4QAYrM> .

[killmenot]

#20 should fix it and seems other functionality works correctly at least in 3 db (redis, gtm and memory). Thanks to @ZuzooVn and his workaround.

I will talk with Rob to merge it but now sure when

[killmenot]

UTF-8 should be already supported on configuration level.

Here is a configuration I use for run gtm tests

  const Gtm = require('nodem').Gtm;
  const db = new Gtm();
  const options = {
    mode: 'strict',
    charset: 'utf-8'
  };
  db.open(options)

And this test case works for me well:

var expected = {
  baz: 'Thắng Nguyễn'
};

var foo = {
  baz: 'Thắng Nguyễn'
};

documentNode.$('foo').delete();
documentNode.$('foo').setDocument(foo);

var actual = documentNode.$('foo').getDocument();

expect(actual).toEqual(expected);

Other db providers are not tested but I know that redis db provider lib needs to be updated to support this

NOTE: Read more about character encoding here: https://github.com/dlwicksell/nodem#important-notes