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

Case issue on postgres table names #310

Closed
ian-at-cos opened this issue Jul 3, 2024 · 2 comments
Closed

Case issue on postgres table names #310

ian-at-cos opened this issue Jul 3, 2024 · 2 comments

Comments

@ian-at-cos
Copy link

I have the following in my data contract:

models:
  PaymentLinksV1:
    type: table
    fields:
    ...

However when I try to test the contract, I receive this error:
Screenshot 2024-07-03 at 13 37 42

It seems the YAML is correctly parsed, and case of the table name (PaymentLinksV1) is correctly retained - but then in the error message (relation does not exist) the table name is shown lowercase.

It looks like the table is not found because at some point the tablename is converted to lowercase. I suggest this because if I try this same test with a postgres table that has a lowercase-only name, I don't have this problem.

I would appreciate advice on this, if it's an issue or something I've missed. If the answer is just to only use lowercase table names then that's an option too.

@jochenchrist
Copy link
Contributor

Yes, I confirm this is a bug. Working on it.

@jochenchrist
Copy link
Contributor

Thanks for reporting.
Fix will come with v0.10.9.

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

2 participants