You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mapper generates integers however ("30"^^<http://www.w3.org/2001/XMLSchema#integer>) and I think that's correct behaviour for columns with type INT, although the spec only mentions SMALLINT, INTEGER and BIGINT, and does not mention INT directly.
The expected output would be correct if the column type was FLOAT, REAL or DOUBLE PRECISION.
So I propose to change the expected output to use xsd:integer instead of xsd:double.
The text was updated successfully, but these errors were encountered:
The contents of the database are created like this:
And the expected output contains things like this:
The mapper generates integers however (
"30"^^<http://www.w3.org/2001/XMLSchema#integer>
) and I think that's correct behaviour for columns with type INT, although the spec only mentions SMALLINT, INTEGER and BIGINT, and does not mention INT directly.The expected output would be correct if the column type was FLOAT, REAL or DOUBLE PRECISION.
So I propose to change the expected output to use
xsd:integer
instead ofxsd:double
.The text was updated successfully, but these errors were encountered: