. "VirtODBCJDBCUTF8Set" . . . . . "2017-06-13T05:41:17Z" . "2017-06-13T05:41:17Z" . . . . "VirtODBCJDBCUTF8Set" . . . "ccfaff1219f79c6de1cd1bd930ab7d38" . "---++Set utf8 for ODBC or JDBC connections\n\n\n 'charset=utf-8' \n\n\n\n\n---+++JDBC Driver\n\nThe connect option for charset of the JDBC driver causes java string \nobject to be sent as utf8 to server where it will be written as utf8 \nencoded narrow string into rdf object and respectively into rdf \nstore. The process is a bit complicated but essentially the string \ncomes to server as utf8. In situation where a narrow charset is used \nthe string object will be encoded in the narrow charset string, we \ndon't want this when working against rdf since it works with utf8, \nthus this special connection option from above should be used.\n\n\n---+++ODBC Driver\n\nAs for ODBC, the client should not set a special charset, then utf8 \nwill be sent to client as is and rdf store will receive utf8 string, \nwill be same as in java, just redland driver must ensure what comes \nin to be utf8 or to be recoded as utf8. When getting string from rdf \nback to odbc it will be utf8 string, thus on output redland driver \nshould take care to recode or just return utf8 depends how interface \nof redland is. That said, odbc when send a utf8 to server and uses default server \nencoding server will get utf8 , when asking for this data will get \nsame back i.e. utf8. As for NVARCHAR cols and utf8, if nvarchar needs to be utilized, then charset_recode \nneeds to be used on client side with current server/driver, but this not affects rdf store dml and queries." . . . "2017-06-13T05:41:17.290300"^^ . "2017-06-13T05:41:17.290300"^^ . . "VirtODBCJDBCUTF8Set" .