Type inference issues in the Postgres engine

[adelsz]

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 #197
• Count aggregate function is number | null, should be just number #191
• Parameter type inference is order dependent #354
• Coalesce type generated as nullable even if it's not #327
• UNION operator makes all fields on result type nullable #431
• Array spread and pick unexpected type when using select from values #313
• Types in array spread are not infered, e.g. in multiple update #450
• Outer joins and nullable #201

[petetnt]

Another possible meta issue, literal column values end up being type | null.

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
}