Well, the Specification still needs to be 'translated' when there is an underlying Query engine (most cases for performance). I am not happy to see a trend that "always use underlying systems query mechanism", since that binds very hard to a particular implementation (trying to help people not shooting themselves in the foot). And making 'programmable' native queries is a very dangerous tool which people quickly go to... Just saying!
So I am +0 to -0 on this one... On Mon, Jun 20, 2011 at 2:47 PM, Rickard Öberg <[email protected]> wrote: > If you are using Queries with an Iterable<Entity>, this specifically means > that you can literally implement that Specification<Entity> any way you want > to, with custom code and whatnot. > > For variables, they will still be there, but just easier to handle. > > The biggie comes with custom operators and queries. I *think* that the > NamedEntityFinder thing will go away completely, simply because it can be > done this way instead: > queryBuilder.where(SesameOperators.sparql("SPARQL goes here")); > or > queryBuilder.where(SesameOperators.serql("SERQL goes here")); > > The Sesame-based EntityFinder can detect these custom operators and just use > the strings as-is, with the correct internal query language. This also opens > up for using code-only queries like what Neo4j does, as the Specification > can literally wrap anything that the internal finder can understand, such as > a Neo4j Traverser. Same goes for the Solr querying mechanism. > > Let me know if you have any issues with these types of changes. > > regards, Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
