Return incorrect results when query integer numbers

[uniqueR-7]

Current Behavior

Write the number 5 of unspecified data type, int type, and long type to the database.

The Java code which writes the numbers to the database is：

Repository db = new SailRepository(new MemoryStore());
IRI john = Values.iri("http://JohnSmith");
IRI mark = Values.iri("http://Mark");
IRI peter = Values.iri("http://Peter");

try (RepositoryConnection conn = db.getConnection()) {
	conn.add(john, FOAF.AGE, Values.literal(5));
	conn.add(mark, FOAF.AGE, Values.literal(String.valueOf(5), XSD.INT));
	conn.add(peter, FOAF.AGE, Values.literal(String.valueOf(5), XSD.LONG));
}

Then query the database for the statement whose literal value is 5.

The SparQL query statement is:

SELECT *
WHERE { ?s ?p 5. }

The query result is empty, instead of the three number 5 in the database.

Expected Behavior

The expected query result is:

?s	?p
<http://JohnSmith>	<http://xmlns.com/foaf/0.1/age>
<http://Mark>	<http://xmlns.com/foaf/0.1/age>
<http://Peter>	<http://xmlns.com/foaf/0.1/age>

Steps To Reproduce

1. Write the following Java code to write the numbers to the database:

   Repository db = new SailRepository(new MemoryStore());
   IRI john = Values.iri("http://JohnSmith");
   IRI mark = Values.iri("http://Mark");
   IRI peter = Values.iri("http://Peter");
   
   try (RepositoryConnection conn = db.getConnection()) {
   	conn.add(john, FOAF.AGE, Values.literal(5));
   	conn.add(mark, FOAF.AGE, Values.literal(String.valueOf(5), XSD.INT));
   	conn.add(peter, FOAF.AGE, Values.literal(String.valueOf(5), XSD.LONG));
   }

2. Execute the following query:

   SELECT *
   WHERE { ?s ?p 5. }
   

   The corresponding Java code is:

   try (RepositoryConnection conn = db.getConnection()) {
   	String queryString = "SELECT * WHERE { ?s ?p 5. }";
   	TupleQuery query = conn.prepareTupleQuery(queryString);
   	TupleQueryResultHandler tsvWriter = new SPARQLResultsTSVWriter(System.out);
   	query.evaluate(tsvWriter);
   }

Version

4.0.0-M1

Are you interested in contributing a solution yourself?

No response

Anything else?

No response

[kenwenzel]

This is not intuitive but correct. Integer literals in SPARQL and Turtle are big integers (xsd:integer) and not xsd:int or xsd:long.
You may take a look at the spec here:
https://www.w3.org/TR/sparql11-query/#QSynLiterals

BTW, if you query for "5"^^xsd:int then you should get two results.

[hmottestad]

Does something like this work?

SELECT *
WHERE { ?s ?p ?o. FILTER(?o = 5) }

[uniqueR-7]

This is not intuitive but correct. Integer literals in SPARQL and Turtle are big integers (xsd:integer) and not xsd:int or xsd:long. You may take a look at the spec here: https://www.w3.org/TR/sparql11-query/#QSynLiterals

BTW, if you query for "5"^^xsd:int then you should get two results.

We know Integer literals in SPARQL are xsd:integer. The issue is that since users can directly write 5 (without explicitly declaring its data type) to database, why could not query it in the same way? Actually, we can get the expected result on Apache Jena.

When we query for "5"^^xsd:int, we indeed get two results. However, since xsd:int and xsd:long are subtypes of xsd:integer, we think graph database systems should support implicit data type conversion for them.

[uniqueR-7]

Does something like this work?

SELECT *
WHERE { ?s ?p ?o. FILTER(?o = 5) }

This SPARQL query can work. Obviously, RDF4j implicitly converts 5 to xsd:int in FILTER operation.
So is it possible to add implicit type conversion to meet users’ query need, just like it can be queried through FILTER?