Hi there!
I once inquired about ORDER BY (using portuguese characters too: UTF-8)
at the DBpedia mailing list, the same thing was happening to me when I
queried DBpedia's SPARQL end point (accented characters going directly
to the end), as I assume conparison is made based on byte order
Hello Alex,
Right now Virtuoso supports traditional SQL collations for single-char
and wide varchars, but not for UTF-8. SPARQL does not offer any
collation handling ATM. I intend to make (better sooner than later)
three things:
1) implement a proxy BIF function that will make a call of specified
Cool!
Ivan Mikhailov, 17-01-2011 13:41:
Hello Alex,
Right now Virtuoso supports traditional SQL collations for single-char
and wide varchars, but not for UTF-8. SPARQL does not offer any
collation handling ATM. I intend to make (better sooner than later)
three things:
1) implement a proxy BIF
Hi Renan,
Is there are reason you are using a 06.01.3126 (6.1.1) open source build
which is from Feb 2010 time , as there have been some order by fixes since his
release ? The latest official open source archive on source forge is 06.01.3128
(6.1.2) from Jul 2010 :
Hi Hugh,
I will update the version (06.01.3128) on my computer and test.
On Virtuoso *06.01.3127* the problem still exist. See below:
Connected to OpenLink Virtuoso
Driver: 06.01.3127 OpenLink Virtuoso ODBC Driver
OpenLink Interactive SQL (Virtuoso), version 0.9849b.
*ORIGINAL (Not use
Hi, Hugh.
I updated the virtuouso to the new version (6.1.3) and continues to happen.
Do you know version name is 06.01.3127-pthreads?
Can you help?
*SQL status();*
REPORT
VARCHAR
___
OpenLink Virtuoso Server
Version
Hi Aldo, Ivan Mikhailov and Virtuoso Users.
Can you help me in using the ORDER BY?
He is by default case and accents sensitive?!
Is there any way to bypass this setting?
Driver: 06.01.3126 OpenLink Virtuoso ODBC Driver
*ORIGINAL (Not use ORDER)*
http://example.com/define
