This HTML5 document contains 30 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
dctermshttp://purl.org/dc/terms/
n17http://vos.openlinksw.com/dataspace/owiki/wiki/VOS/VirtODBCJDBCUTF8Set/sioc.
atomhttp://atomowl.org/ontologies/atomrdf#
foafhttp://xmlns.com/foaf/0.1/
n9http://vos.openlinksw.com/dataspace/services/wiki/
oplhttp://www.openlinksw.com/schema/attribution#
n2http://vos.openlinksw.com/dataspace/owiki/wiki/VOS/
dchttp://purl.org/dc/elements/1.1/
n10http://vos.openlinksw.com/dataspace/dav#
rdfshttp://www.w3.org/2000/01/rdf-schema#
n8http://rdfs.org/sioc/services#
siocthttp://rdfs.org/sioc/types#
n6http://vos.openlinksw.com/dataspace/person/dav#
n4http://vos.openlinksw.com/dataspace/owiki/wiki/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n7http://vos.openlinksw.com/dataspace/owiki#
xsdhhttp://www.w3.org/2001/XMLSchema#
n13http://vos.openlinksw.com/dataspace/person/owiki#
siochttp://rdfs.org/sioc/ns#
Subject Item
n6:this
foaf:made
n2:VirtODBCJDBCUTF8Set
Subject Item
n10:this
sioc:creator_of
n2:VirtODBCJDBCUTF8Set
Subject Item
n9:item
n8:services_of
n2:VirtODBCJDBCUTF8Set
Subject Item
n7:this
sioc:creator_of
n2:VirtODBCJDBCUTF8Set
Subject Item
n4:VOS
sioc:container_of
n2:VirtODBCJDBCUTF8Set
atom:entry
n2:VirtODBCJDBCUTF8Set
atom:contains
n2:VirtODBCJDBCUTF8Set
Subject Item
n2:VOSIndex
sioc:links_to
n2:VirtODBCJDBCUTF8Set
Subject Item
n2:VirtODBCJDBCUTF8Set
rdf:type
sioct:Comment atom:Entry
dcterms:created
2017-06-13T05:41:17.290300
dcterms:modified
2017-06-13T05:41:17.290300
rdfs:label
VirtODBCJDBCUTF8Set
foaf:maker
n13:this n6:this
dc:title
VirtODBCJDBCUTF8Set
opl:isDescribedUsing
n17:rdf
sioc:has_creator
n7:this n10:this
sioc:content
---++Set utf8 for ODBC or JDBC connections <verbatim> 'charset=utf-8' </verbatim> ---+++JDBC Driver The connect option for charset of the JDBC driver causes java string object to be sent as utf8 to server where it will be written as utf8 encoded narrow string into rdf object and respectively into rdf store. The process is a bit complicated but essentially the string comes to server as utf8. In situation where a narrow charset is used the string object will be encoded in the narrow charset string, we don't want this when working against rdf since it works with utf8, thus this special connection option from above should be used. ---+++ODBC Driver As for ODBC, the client should not set a special charset, then utf8 will be sent to client as is and rdf store will receive utf8 string, will be same as in java, just redland driver must ensure what comes in to be utf8 or to be recoded as utf8. When getting string from rdf back to odbc it will be utf8 string, thus on output redland driver should take care to recode or just return utf8 depends how interface of redland is. That said, odbc when send a utf8 to server and uses default server encoding server will get utf8 , when asking for this data will get same back i.e. utf8. As for NVARCHAR cols and utf8, if nvarchar needs to be utilized, then charset_recode needs to be used on client side with current server/driver, but this not affects rdf store dml and queries.
sioc:id
ccfaff1219f79c6de1cd1bd930ab7d38
sioc:link
n2:VirtODBCJDBCUTF8Set
sioc:has_container
n4:VOS
n8:has_services
n9:item
atom:title
VirtODBCJDBCUTF8Set
atom:source
n4:VOS
atom:author
n6:this
atom:published
2017-06-13T05:41:17Z
atom:updated
2017-06-13T05:41:17Z
sioc:topic
n4:VOS