Hello Peter,
FROM is to form default graph only, it does not affect named graphs at
all.
In order to restrict both bindings in default graph and bindings in
graph ?dataset {...}, use
FROM <a> FROM NAMED <a>
FROM <b> FROM NAMED <b>
etc.
Of course, you don't have to keep lists of default and named graphs
identical, just remember that these two lists are (almost) independent.
("Almost" refers to an exception with named graphs specified and no
default graph, see the spec).
Best Regards,
Ivan Mikhailov
OpenLink Software
http://virtuoso.openlinksw.com
On Mon, 2012-01-23 at 12:44 +1100, Peter Secomb wrote:
> Hi everyone,
>
> We have a query as follows:
>
> SELECT ?new_id ?attribute ?value ?id ?dataset
> FROM <a>
> FROM <b>
> FROM <c>
> FROM <d>
> FROM <e>
> WHERE {
> ?s prefixA:ID ?old_id .
> ?old_id ?attribute ? value
> graph ?dataset { ?old_id prefixB:new_attribute ?new_id}
> }
>
> Data is held in graph <d>
> A duplicate graph <d1> exists that is not specified in the FROM
> clause. The other graph's in the FROM clause hold links to the raw
> data in graph <d>
>
> When we run the query the inclusion of the "graph ?dataset {?old_id
> prefixB:new_attribute ?new_id}" line causes data from the unnamed <d1>
> graph to show up in the results along with the requested data from
> graph <d>.
>
> Can anyone help me understand why data from graph <d1> is returned
> even when it is not included in the FROM clause?
>
> Many thanks,
> Peter Secomb
> clearbluewater.com.au
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________ Virtuoso-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users