Re: [dotNetRDF-bugs] Store Manager Remote Query/Update - Sparql Parse always enabled

[Rob V. <rv...@do...>]

It is a bug in the formatting of UNION graph patterns, filed as CORE-402
(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=402) and I'm
working on a fix

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>
Date:  Saturday, 1 March 2014 11:26
To:  "dot...@li..."
<dot...@li...>, Rob Vesse <rv...@do...>
Subject:  Fw: Store Manager Remote Query/Update - Sparql Parse always
enabled

> I think there is a parsing problem when using store manager from tools_103
> (and previous versions) with UNION.
> The following query in store manager (using sparql query/update connection):
> ----------------------------------------
> SELECT ?b ?c 
> WHERE 
> {
>   {
>     GRAPH <http://AliceIRI>
>     {
>     <http://local.virt/foo> ?b ?c}
>   }
>   UNION
>   { 
>     GRAPH <http://BobIRI> {
>     <http://local.virt/foo> ?b ?c}
>   }
>  
> }
>  --------------------------------------------
> 
> is sent to the sparql endpoint as (notice removal of "{}" before UNION):
> 
> --------------------------------------------------------
> SELECT ?b ?c
> WHERE
> {
>   GRAPH <http://aliceiri/> { <http://local.virt/foo> ?b ?c . }
>   UNION
>   {
>     GRAPH <http://bobiri/> { <http://local.virt/foo> ?b ?c . }
>   }
> }
>  --------------------------------------------
> and of course it fails on the server.
> I forwarded to prev message because this could be fixed by fixing the parser
> or by allowing to skip local parsing.
> 
> If this isn't fixed already is a dev branch, I could fix the "skip local
> parsing" in a dnr fork, since I have to fix this anyway because at this point
> I can't write the query.
> 
> 
>  
>  
>  
>   On Sunday, December 22, 2013 3:26 PM, Eugen F <feu...@ya...> wrote:
>   
>   
> 
> When using store manager(query/update endpoint) with custom sparql queries it
> always performs parsing because SparqlConnector _skipLocalParsing is always
> false(UI code skips parsing, but the connector enforces it).
> 
> Maybe it's better for the connector to catch parsing error and default to no
> parsing (same as UI/manager code).
> 
> 
>   
>  
>   
>