Issue with VALUES in Stardog 3.0

[Tze-John Tang]

I am querying a store with multiple named graphs.  I came across where results returned using the VALUES keyword is inconsistent.  Here is an example query, executed with Reasoning turned off.

select *

where

{

  graph ?g {

    

?s a owl:Class .

    VALUES (?s) {

      (<http://schemas.abbvienet.com/ontologies/infrastructure.owl#blah>)

      (<http://schemas.abbvienet.com/ontologies/infrastructure.owl#blahblah>)

    }

  }

}

If there is a graph that contains these class definitions, then the correct ?g value is returned, if these are not defined anywhere, then nothing is returned, which is correct.  However, if I change select * to select ?g or select distinct ?g, then any graph that contains class definitions is returned. This is not what I am expecting.  Is this correct behavior?

Thanks,

-tj

[Evren Sirin]

No, this is not the correct behavior. It is not a generic issue with
VALUES keyword but happens when the variable bound by VALUES is used
only in one triple pattern in the query and not included in the
SELECT. We'll fix this in the next release.

Best,
Evren

> --
> -- --
> You received this message because you are subscribed to the C&P "Stardog"
> group.
> To post to this group, send email to sta...@clarkparsia.com
> To unsubscribe from this group, send email to
> stardog+u...@clarkparsia.com
> For more options, visit this group at
> http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en