Hi Folks,
I was debugging a problem I was having with a query, and I think I have
stumbled on a bug in TBL.
Here is a very simple demonstration of something behaving differently between
TBC and TBL:
SELECT *
WHERE {
OPTIONAL {
?x rdf:value "dog" .
} .
BIND (IF(bound(?x), "x is bound!", "x is not bound!") AS ?result) .
}
If you run this in TBC, it binds the value “x is not bound!” to ?result, as you
might expect, and the value of ?x is unbound.
However, running this on our TBL instance on AWS, you get ?x bound to “x is not
bound!” and ?result is not bound. This is very unexpected. We’re running
version 4.2.1 of TBL, and 4.3.0 of TBC, but I’m surprised if the behavior of IF
changed between 4.2 and 4.3
Any thoughts? Can you reproduce this effect?
- Steve
Steven R. Ray, Ph.D.
Distinguished Research Fellow
Carnegie Mellon University
NASA Research Park
Building 23 (MS 23-11)
P.O. Box 1
Moffett Field, CA 94305-0001
Email: [email protected]
Phone: (650) 587-3780
Cell: (202) 316-6481
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight,
SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.