Andy, Just to say this is a low priority issue for us. The query works fine for what we need with the second binding in the sub query. It was more of a heads up and trying to understand what was wrong with doing it the other way.
Cheers Rob On Fri, Feb 1, 2013 at 3:38 PM, Andy Seaborne <[email protected]> wrote: > On 01/02/13 15:07, Rob Walpole wrote: > >> Hi Andy, >> >> On Fri, Feb 1, 2013 at 12:16 PM, Andy Seaborne <[email protected]> wrote: >> >> Rob - I notice you use rdfs:member which is a calculated property in ARQ. >>> >>> There is a bug in ARQ (JENA-340) which means this isn't handled as a >>> calculated property inside a FILTER. >>> >> >> >> You have: >>> >>> FILTER EXISTS { ?export rdfs:member ?ancestor } . >>> >>> >> On it's own this doesn't seem to cause us any problems... perhaps because >> we are specifically inserting these triples into TDB rather than relying >> on >> them being calculated? >> > > good - it checks for both cases - explicit and implicit > > Nasty things RDF alt/bag/seq from the POV of a database. > > Andy > > >> Thanks >> Rob >> >> > -- Rob Walpole Email [email protected] Tel. +44 (0)7969 869881 Skype: RobertWalpolehttp://www.linkedin.com/in/robwalpole
