-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Type inference issues in the Postgres engine #375
Comments
This was referenced Dec 4, 2021
adelsz
changed the title
Type inference bugs in Postgres engine
Type inference issues in the Postgres engine
Jan 28, 2023
Another possible meta issue, literal column values end up being select id, 'foo' as foovalue, 1 as barvalue from 'bar'; Result: type Bar = {
id: number
foovalue: string | null
barvalue: number | null
} Expected: type Bar = {
id: number
foovalue: string
barvalue: number
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a meta issue to track all type inference issues occurring inside the PostgreSQL engine.
At this stage we can't solve them inside pgTyped without building a more powerful SQL parser.
Ideally they should be fixed inside PostgreSQL.
Issues:
coalesce
with a literal, non-null value is generating a| null
type #197number | null
, should be justnumber
#191Array spread and pick
unexpected type when usingselect from values
#313The text was updated successfully, but these errors were encountered: