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 reason is that any extension in FROM/FROM NAMED interferes with graph-level security that is complicated by itself and, more important, the debugging is complicated. While other features should work when needed, security should prevent things from working when unwanted; I'm an engineer, not a turnkey, so that sort of thinking damage my brains in a quite unusual way :) > And, on a related note. The other low hanging fruit: > i++; i+=3 That's a long-waiting feature, I'm going to add it since 2001. However the accurate implementation of the feature should deal with UDT members as well, that requires some amount of coding. A trivial "macroexpansion" like "i := i+1; i := i+3" does not work there, because functions inside "i" will be calculated twice. Best Regards, Ivan Mikhailov OpenLink Software http://virtuoso.openlinksw.com
