Hi Sergey
Thank you again for your feedback.
I have noticed now that even the Virtuoso stored procedures
DB.DBA.csv_register()
and DB.DBA.csv_loader_run() are not compatible with unicode text. So it
seems that my ETL module related to the data loading has to be
reimplemented using the drivers you
On 03/23/2017 12:45 AM, Beppe Mazzola wrote:
Thanks Sergey
Your suggestion inspired me to do some more trials.
Declaring the text column
VARCHAR(3000) instead of NVARCHAR(1000)
the problem disappears, but I have to increase the column size because somehow Virtuoso recognizes the text as non-L
Thanks Sergey
Your suggestion inspired me to do some more trials.
Declaring the text column
VARCHAR(3000) instead of NVARCHAR(1000)
the problem disappears, but I have to increase the column size because
somehow Virtuoso recognizes the text as non-Latin and uses UTF-8 that
occupies m
On 03/21/2017 04:42 AM, Beppe Mazzola wrote:
> Related to the problem I have about storing non-Latin character in Virtuoso
> RDB, I see now that I haven't provided all the info related to it.
>
> So it was not evident that the Hungarian text written in the DB was not the
> same read from it immed
Related to the problem I have about storing non-Latin character in Virtuoso
RDB, I see now that I haven't provided all the info related to it.
So it was not evident that the Hungarian text written in the DB was not the
same read from it immediately after, despite the Virtuoso UTF-8 set-up has
been
Even if the database is configured for UTF-8 it still matters how you insert
the data. I’ve had similar problems in the past where the issue was that the
connection to the database was using a different encoding. If memory serves you
have to explicitly set the character set on your ODBC/JDBC/ADO
Hi Hugh
This should reproduce the problem. In my Virtuoso installation the
Bulgarian text inserted in the test table is different to the one displayed
as a result of the select.
1) Create a user with name test with the following setting.
[image: Immagine incorporata 1]
2) log in as user test
3
Hi Beppe,
That should be all that is required on the server for Unicode / UTF-8 support.
Do you have a test case for recreating the problem being observed, which should
show how the data is being inserted and the queried ?
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc
