Hello Alexander, I've re-tested the example and found that the truncation happens at data transmission between server and client. No one of ODBC/UDBC/IODBC support typed RDF boxes, so data are not transferred properly. One of possible workarounds is querying string value and datatype separately:
SQL> sparql select (str(?o)) as ?text_of_o, (datatype(?o)) as ?dt_of_o from <http://graph> where {?s ?p ?o} order by ?s; text_of_o dt_of_o VARCHAR VARCHAR _______________________________________________________________________________ 12345678901234567890 this text is not displayed http://www.w3.org/2001/XMLSchema#string We'll try to invent something to improve the behavior. Best Regards, Ivan Mikhailov, OpenLink Software http://virtuoso.openlinksw.com P.S. Note that plain untyped string and string of explicit type xsd:string are two different things. You may wish to use untyped strings and keep ODBC serialization happy. On Wed, 2008-10-01 at 01:32 +0400, Alexander I. Gordeev wrote: > Hi All! > > I've found a bug which is described in subj. An easy way to reproduce (works > on default empty database): > > 1. Add a triple where object is a string literal with more then 20 bytes in > length. > > 2. Run a query: > sparql select ?o from <http://graph> where {?s ?p ?o} order by ?s > > The output will be truncated to 20 bytes. > Attached some logs.
