Uditha Atukorala

Hmm, looks like the error is coming from [NaN](https://github.com/nodejs/nan). @saraf, could you please let me know `node` and `npm` versions you are using?

@leosurban, can you give a sample SQL script to create a DB and a table with some data for me to test this out (similar to [test/support/test-db.sql](https://github.com/nukedzn/node-informix/blob/master/test/support/test-db.sql))? Most likely this...

It seems to work OK with UTF-8. Using dbaccess (data from `LocaleTest.odt`): ``` create table exampletable ( id integer not null, somename nvarchar(100) not null, somedate date not null, primary...

@leosurban, can you set the windows command prompt and CLIENT_LOCAL to utf-8 and check whether it resolves the issue? Although ESQL/C support CLIENT_LOCAL when retrieving data, within Node.js all strings...

I'm using Linux UTF-8. A quick search seem to suggest you'll need Lucida Console font as well for UTF-8 support on windows command prompt which I assume you are using?...

Looks like there's a conversion issue somewhere on windows. Don't have access to a windows PC now to debug this but will try to take a look later this week.

Tested this on a Windows 7 VM and encoding works fine. Node.js command prompt:  ConEmu shell:  However my DB is in en_us.819 (default?). ``` > select * from...

So need to check, - [x] Is this an issue with DB_LOCALE being cs_CZ.cp1250? - cs_CZ.UTF8 seems to work, most likely this issue is related to some additional features presented...

Took a little bit of time to update my Informix images to include extended GLS support but finally managed to reproduce this issue on Linux 😃. 1. `DB_LOCALE=cs_CZ.UTF8` ``` >...

I can't get cs_CZ.cp1250, cs_CZ.pc-latin-2, cs_CZ.8859-2 locales to work. They throw -23101/-23104 errors on my 12.10 FC8DE installation (client SDK 4.10 FC8DE) even through I selected all available GLS components...