I think I understand what the problem is. First of all, I noticed that the behavior worked as expected with SELECT queries and I then realized that for DESCRIBE we are using handlers which on their turn use SELECT queries without the FROM/FROM NAMED clauses, which would explain the behavior. So it is probably a non-issue
Simon From: Simon Helsen/Toronto/IBM To: [email protected] Date: 07/10/2012 04:31 PM Subject: FROM/FROM NAMED in tdb Hi everyone, I was just revisiting a number of tests and I noticed that currently, we employ a hack for FROM and FROM NAMED queries, essentially creating an intermediate in-memory dataset to execute such queries. However, when I tried to remove this mechanism and directly execute a FROM/FROM NAMED query (in my particular test, it was a DESCRIBE) on a tdb dataset, I noticed the query's scope is not actually reduced to the graphs in the FROM NAMED (I am running with defaultUnionGraph=true). Is this a known issue or limitation? Or is there something else I am missing to get this work correctly? thanks Simon
