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.

Sign up for GitHub

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

Jump to bottom

data source test: SQL CHAR datatype #6

Open
bjdmeest opened this issue Mar 8, 2024 · 2 comments
Open

data source test: SQL CHAR datatype #6

bjdmeest opened this issue Mar 8, 2024 · 2 comments
Labels
help wanted Extra attention is needed question Further information is requested working-group Issues to address in the WG

Comments

@bjdmeest
Copy link
Member

bjdmeest commented Mar 8, 2024

Generation of triples by using CHAR datatype column, resulting RDF literal is space-padded. (specification reference)
@bjdmeest bjdmeest mentioned this issue Mar 8, 2024
Closed
4 tasks
@DylanVanAssche
Copy link
Contributor

The discussion from #100 is that this is SQL vendor specific behavior.
What do we do about this?

One of the suggestions is to have test-cases that are ANSI-SQL and then when a vendor deviates from ANSI, it has its own test-case. However, this will give for this case that MySQL will never have space-padding, contradicting the specification reference.

@DylanVanAssche DylanVanAssche mentioned this issue Mar 8, 2024
Closed
@DylanVanAssche DylanVanAssche added help wanted Extra attention is needed question Further information is requested labels Mar 11, 2024
@DylanVanAssche
Copy link
Contributor

Shouldn't this be moved to rml-io-registry? @bjdmeest

@DylanVanAssche DylanVanAssche added the working-group Issues to address in the WG label Jun 20, 2024
@DylanVanAssche DylanVanAssche transferred this issue from kg-construct/rml-io Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed question Further information is requested working-group Issues to address in the WG
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bjdmeest @DylanVanAssche