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

PostgreSQL domains: INTEGER column (via DOMAIN definition) is mapped to string #207

Open
mperdikeas opened this issue Oct 10, 2024 · 0 comments

Comments

@mperdikeas
Copy link

mperdikeas commented Oct 10, 2024

I have a column in PostgreSQL:

person_type: INTEGER

This is mapped to a JavaScript number | null just as it should be.

If instead, the column is defined via a PostgreSQL domain that is itself simply an alias for INTEGER, or INT4 like so:

CREATE DOMAIN FOREIGN_KEY AS INTEGER
...
person_type: FOREIGN_KEY

Then it is mapped as string | null. In fact this behavior remains even if the domain is aliased to SMALLINT

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
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