Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hello Ricardo, This is my fault, the feature may cause inadequate error diagnostics depending on server building options and roll of dice. The attached diff contain the fix, you may apply it to libsrc/Wi directory to not wait for next release. Best Regards, Ivan Mikhailov OpenLink Software http:

Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hi We've installed installed virtuoso 6.1. One of the new features on the list is Added support for expressions in LIMIT and OFFSET clauses So we tried to write again this query inside of a for in a virtuoso procedure. sparql select distinct ?documentId ?title ?abstract ?title_relevance

Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hi Ivan, On Thu, Jan 21, 2010 at 12:46 PM, Ivan Mikhailov wrote: > Hello Aldo, > >> OK, and what about: >> [10]* DefaultGraphClause       ::=  SourceSelector SpongeOptionList? >> [11]* NamedGraphClause         ::=  'NAMED' SourceSelector SpongeOptionList? >> ? > > That costs much more than an ext

Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hello Aldo, > OK, and what about: > [10]* DefaultGraphClause ::= SourceSelector SpongeOptionList? > [11]* NamedGraphClause ::= 'NAMED' SourceSelector SpongeOptionList? > ? That costs much more than an extension for LIMIT/OFFSET (that is implemented already, right today). The reaso

Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hi, On Thu, Jan 21, 2010 at 11:05 AM, Ricardo Z wrote: > Hi Ivan. > > Thanks for the quick response. > So the problem is related to the sparql expresions parser. > > I think the change of the rule of this parser it should be consistent with > the definition of the others elements on the sparql ex

Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hi Ivan. Thanks for the quick response. So the problem is related to the sparql expresions parser. I think the change of the rule of this parser it should be consistent with the definition of the others elements on the sparql expresion in order to obtain a coherent behaviour. For example, I thin

Re: [Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hello Ricardo, > for(sparql select > ... > order by desc(?relevance) limit 50 offset ?:offsetValue > ) do { > ... > } > ... > > Its warn. > syntax error at '?:offsetValue' at ')' before 'do' In original SPARQL the syntax was [19]OffsetClause ::= 'OFFSET' INTEGER and I did not

[Virtuoso-users] Problem with virtuoso procedure in a sparql query.

Hi. We are embedding a sparql query into a for of virtuoso procedure. Everything works great if we do the following. Focus on the value of the offset: ... for(sparql select distinct ?documentId ?title ?abstract ?relevance ?classification from where { ?do