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

Describe special behavior of each RDBM? #2

Open
marioscrock opened this issue May 14, 2024 · 2 comments
Open

Describe special behavior of each RDBM? #2

marioscrock opened this issue May 14, 2024 · 2 comments
Assignees
Labels
question Further information is requested working-group Issues to address in the WG

Comments

@marioscrock
Copy link

The table "IOUs" is not found since the .sql file used for database initialization does not put the table name between double quotes and Postgres by default initializes the table as "ious" (lowercase).

I solved this issue by forcing a lowercase conversion for table names extracted from RML if the source is a Postgres DB. However, I don't know if this is a good assumption or if it would be better to update the test case.

@DylanVanAssche
Copy link
Contributor

Interesting! I have seen this problem like a lot. IMO, we should even define this as part of the rml-io-registry where we define for each reference formulation 'special' handling. We cannot change the behavior of various RDBMS vendors so we have to define how to handle these cases I guess?

@dachafra
Copy link
Member

dachafra commented Jul 3, 2024

I agree with you @DylanVanAssche, if you think it is more related to the rml-io-registry, we can transfer the issue to that repository.

@dachafra dachafra changed the title Issue with Postgres test cases RMLTC0005a-PostgreSQL and RMLTC0005b-PostgreSQL Describe special behavior of each RDBM? Jul 4, 2024
@dachafra dachafra added the question Further information is requested label Jul 4, 2024
@dachafra dachafra transferred this issue from kg-construct/rml-core Jul 4, 2024
@dachafra dachafra added the working-group Issues to address in the WG label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested working-group Issues to address in the WG
Projects
None yet
Development

No branches or pull requests

3 participants