Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RMLTC0012e-MySQL: expected output has double-precision numbers, while it should have integers #41

Open
thomas-delva opened this issue Apr 12, 2021 · 0 comments

Comments

@thomas-delva
Copy link

The contents of the database are created like this:

CREATE TABLE IOUs (fname VARCHAR(20), lname VARCHAR(20), amount INT);
INSERT INTO IOUs (fname, lname, amount) VALUES ('Bob', 'Smith', 30);

And the expected output contains things like this:

_:Bob_Smith_30 <http://example.com/base/IOUs#amount> "3.0E1"^^<http://www.w3.org/2001/XMLSchema#double> .

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant