Hi, On Thu, Jan 21, 2010 at 11:05 AM, Ricardo Z <[email protected]> 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 expresion in order to > obtain a coherent behaviour. > > For example, I think a user expect that if can be used external variables to > fix a value of a subject, predicate, etc. Also is expected to do it on the > offset, limit, etc.
OK, and what about: [10]* DefaultGraphClause ::= SourceSelector SpongeOptionList? [11]* NamedGraphClause ::= 'NAMED' SourceSelector SpongeOptionList? ? We have been using exec() when we hit a wall, but count me in as a second vote. This is a common usecase ;) And, on a related note. The other low hanging fruit: i++; i+=3 ;) Regards, A > > I understand that to change the rule > OffsetClause ::= 'OFFSET' INTEGER > to > OffsetClause ::= 'OFFSET' expression > > It would be solve my problem, but I dont know if this is consistent with the > rest of the elements. > Maybe there is more particular types of expresions that are allowed for > those elements (such subject or predicate). I think it sould be use the same > type of rule in the case of the offset and maybe what you seggest it is, I > dont know. > > > Best. > Z > > > > On Thu, Jan 21, 2010 at 6:37 AM, Ivan Mikhailov <[email protected]> > wrote: >> >> 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 extend it to something like >> [19*] OffsetClause ::= 'OFFSET' expression >> >> because in that time I was unable to efficiently prohibit bad things >> like an offset expression that depends on result values. You're the >> first who ask about the extension and it can be implemented now, so >> expressions will be permitted in the next version. Chances are that you >> can get a patch even before that if you specify the exact version you >> want to see patched. >> >> Best Regards, >> >> Ivan Mikhailov >> OpenLink Software >> http://virtuoso.openlinksw.com >> >> > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Virtuoso-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtuoso-users > > -- Aldo Bucchi skype:aldo.bucchi http://www.univrz.com/ http://aldobucchi.com/ PRIVILEGED AND CONFIDENTIAL INFORMATION This message is only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, please do not distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail.
