Regression: inference of subquery aliased field name incorrect

[karlhorky]

Describe the bug

SafeQL infers that the field in the subquery is id and not the aliased name rsvped:

// 💥 Query has incorrect type annotation.
//    Expected: { rsvped: boolean }[]
//      Actual: { id: number }[]
await sql<{ rsvped: boolean }[]>`
  SELECT
    x.*
  FROM
    (
      SELECT
        event_rsvps.id IS NOT NULL AS rsvped
      FROM
        event_rsvps
    ) x
`

Workaround

1. Use explicit field names (x.rsvped instead of x.*)
2. Switch boolean type to boolean | null (not accurate, but I think this is a separate SafeQL nullability inference error)

// ✅
await sql<{ rsvped: boolean | null }[]>`
  SELECT
    x.rsvped
  FROM
    (
      SELECT
        event_rsvps.id IS NOT NULL AS rsvped
      FROM
        event_rsvps
    ) x
`

To Reproduce

See above

Expected behavior

Inference of the aliased name rsvped in the subquery

Screenshots

--

Desktop (please complete the following information):

• OS: macOS Sequoia 15.2 (24C101)
• PostgreSQL version 14.13
• Version 3.6.2

Additional context

Originally introduced in this PR:

• fix: correct type inference for arithmetic operations #359

[Newbie012]

fixed in 3.6.3

[karlhorky]

Hmm, still seeing this with @ts-safeql/[email protected] 🤔

// 💥 Query has incorrect type annotation.
//    Expected: { rsvped: boolean }[]
//      Actual: { id: number }[]
await sql<{ rsvped: boolean }[]>`
  SELECT
    x.*
  FROM
    (
      SELECT
        event_rsvps.id IS NOT NULL AS rsvped
      FROM
        event_rsvps
    ) x
`

Here's the minimal table definition, in case that works for reproducing for you:

CREATE TABLE event_rsvps (
  id integer PRIMARY KEY GENERATED ALWAYS AS IDENTITY
);