Hi Rob,

We certainly would recommend you test against the updated server from the 
snapshot which should not have this problem ...

Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
Support: http://support.openlinksw.com
Forums: http://boards.openlinksw.com/support
Twitter: http://twitter.com/OpenLink

On 7 Mar 2011, at 09:50, Rob Vesse wrote:

> Hi Hugh
> 
> I think I have the 6.1.1 release on one machine and 6.1.2 on another.  
> Although you provided me the 6.1.3 snapshot I only looked at the ADO.Net 
> provider code and did not actually install the updated server.
> 
> If this is fixed in the 6.1.3 build then feel free to ignore this bug report.
> 
> Rob
> 
> From: "Hugh Williams" <hwilli...@openlinksw.com>
> Sent: 04 March 2011 16:02
> To: rve...@vdesign-studios.com
> Subject: Re: [Virtuoso-users] Major bug with Virtuoso SPARQL Results
> 
> Hi Rob,
> 
> I presume the 6.1.3127 built you refer to is the open source 18th Feb 2011 
> snapshot we  made available to you whose version is actually 6.1.3-rc6.3127 ? 
> Note the open source and commercial products do not have the same version 
> number sequences and thus the 06.02.3128 commercial builds on the web 
> currently are from September 2010 and thus older than the snapshot you are 
> using. SO please confirm you are running the 18th Feb snapshot and we can 
> attempt a recreation against that ...
> 
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software
> Web: http://www.openlinksw.com
> Support: http://support.openlinksw.com
> Forums: http://boards.openlinksw.com/support
> Twitter: http://twitter.com/OpenLink
> 
> On 4 Mar 2011, at 09:22, Rob Vesse wrote:
> 
>> Hi
>> 
>> I have attached a file which is a trace of the request produced by using 
>> TamperData in Firefox.  My version of Virtuoso is 6.1.3127 so maybe it is 
>> fixed in the 6.2 releases?
>> 
>> I can also reproduce this error using SPASQL by making the request via the 
>> ADO.Net provider.
>> 
>> This is the XML output I get:
>> 
>> <sparql xmlns="http://www.w3.org/2005/sparql-results#"; 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
>> xsi:schemaLocation="http://www.w3.org/2001/sw/DataAccess/rf1/result2.xsd";>
>>  <head>
>>   <variable name="g"/>
>>  </head>
>>  <results distinct="false" ordered="true">
>>   <result>
>>    <binding 
>> name="g"><literal>http://www.openlinksw.com/schemas/virtrdf#</literal></binding>
>>   </result>
>>   <result>
>>    <binding name="g"><literal>http://localhost:8890/DAV</literal></binding>
>>   </result>
>>   <result>
>>    <binding 
>> name="g"><literal>http://www.w3.org/2002/07/owl#</literal></binding>
>>   </result>
>>   <result>
>>    <binding 
>> name="g"><literal>http://localhost/VirtuosoTest</literal></binding>
>>   </result>
>>   <result>
>>    <binding 
>> name="g"><literal>http://localhost/TurtleImportTest</literal></binding>
>>   </result>
>>   <result>
>>    <binding name="g"><literal>http://example.org/</literal></binding>
>>   </result>
>>   <result>
>>    <binding name="g"><literal>http://example.org/bnodes/</literal></binding>
>>   </result>
>>   <result>
>>    <binding 
>> name="g"><literal>http://example.org/VirtuosoEncodingTest</literal></binding>
>>   </result>
>>  </results>
>> </sparql>
>> 
>> I will try out the 6.2 release and see if that makes a difference
>> 
>> Rob
>> 
>> From: "Sebastian Trüg" <tr...@kde.org>
>> Sent: 04 March 2011 08:41
>> To: virtuoso-users@lists.sourceforge.net
>> Subject: Re: [Virtuoso-users] Major bug with Virtuoso SPARQL Results
>> 
>> See also this closed bug report:
>> http://sourceforge.net/tracker/?func=detail&aid=2995846&group_id=161622&atid=820574
>> 
>> On 03/02/2011 02:42 PM, Rob Vesse wrote:
>> > 
>> > Hi all
>> > 
>> > I've found what appears to be a major bug with Virtuoso's SPARQL results
>> > for one specific query namely:
>> > 
>> > SELECT DISTINCT ?g WHERE { GRAPH ?g { ?s ?p ?o } }
>> > 
>> > When this query is executed results come back as elements in
>> > the XML results rather than as elements. If you remove the
>> > DISTINCT modifier then they come back as fine.
>> > 
>> > I assume that this is a bug in your optimisation of the above query
>> > since the above is commonly optimised specially since it is often used
>> > to list the graphs of a SPARQL endpoint.
>> > 
>> > Regards,
>> > 
>> > Rob Vesse
>> > 
>> > 
>> > 
>> > ------------------------------------------------------------------------------
>> > Free Software Download: Index, Search & Analyze Logs and other IT data in 
>> > Real-Time with Splunk. Collect, index and harness all the fast moving IT 
>> > data 
>> > generated by your applications, servers and devices whether physical, 
>> > virtual
>> > or in the cloud. Deliver compliance at lower cost and gain new business 
>> > insights. http://p.sf.net/sfu/splunk-dev2dev 
>> > 
>> > 
>> > 
>> > _______________________________________________
>> > Virtuoso-users mailing list
>> > Virtuoso-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>> 
>> ------------------------------------------------------------------------------
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. http://p.sf.net/sfu/progress-d2d
>> _______________________________________________
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>> 
>> <virtuoso-bug-report.txt>------------------------------------------------------------------------------
>> What You Don't Know About Data Connectivity CAN Hurt You
>> This paper provides an overview of data connectivity, details
>> its effect on application quality, and explores various alternative
>> solutions. 
>> http://p.sf.net/sfu/progress-d2d_______________________________________________
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
> 
> 

Reply via email to