While an error is printed , the code drop through an processes it
anyway. The code seems to reflect an attempt to insert constants in the
query ... but that's not active so the whole thing is a no-op for SDB.
Looks like the error can be ignored.
Does it produce the wrong answers at all?
Andy
On 23/10/17 15:43, Andy Seaborne wrote:
Hi Rachel,
That's a very old version of SDB but the bug is still there (I just
tested). Actually, I'm not sure it is a bug because I get the right
answers. Does it produce the wrong answers at all?
The latest versions are all "3.4.0" - and you need to reload data when
migrating.
Andy
https://jena.apache.org/documentation/migrate_jena2_jena3.html
On 23/10/17 00:21, Rachel Han wrote:
Hi list,
I am quite new to jena/sparql. Recently I have spotted an error while
running any sparql query with "values" keyword.
It gave me this line in the log : ERROR [TransformSDB] OpTable : Not join
identity
e.g.
PREFIX dm: <http://learningsparql.com/ns/demo#>
SELECT * WHERE { }
VALUES (?color ?direction) {
( dm:red "north" )
( dm:blue "west" )
}
We are using
jena 2.10.1,
jena-arq 2.10.1,
jena-sdb 1.3.6,
jena-tdb 0.10.0,
jena-iri 0.9.6
mysql database version 5.7
sparql version 1.1
Would anyone have the same issue like this? Please help :)
Thanks in advance.
Cheers,
Rachel
