Re: [Rdfapi-php-interest] SparqlEngineDb: current status

[Christian W. <cw...@cw...>]

> In the last two weeks I have addressed LIMIT and UNION support in my
> database-driven sparql engine. For this, I extended the current sparql
> parser to parse LIMITs and convert them into a nice tree. The tree make=
s
> it easily possible to replace the current code in the old, memory based=

> SparqlEngine limit handling code (which has a barn-door wide security
> hole currently by using the evil eval() function to verify limit
> clauses) by a secure alternative. I didn't have time to do this yet.
> SparqlEngineDb's LIMIT support is nearly finished; the 41 limit unit
> tests pass (with the exception of three which are either not possible t=
o
> implement, or are not worth the required work [which would be huge] and=

> would slow down the queries badly. All of them are edge cases.).
I don't know why I confuse LIMIT with FILTER when talking or writing. I
meant I implemented full FILTER support.

--=20
Regards/Mit freundlichen Gr=FC=DFen
Christian Weiske