NULLable interval column inferred as `string` instead of `string | null`

[icopp]

Describe the bug

It looks like for some reason, on the latest Supabase CLI version (supabase version 2.58.5), interval columns are getting inferred as string only, ignoring the nullability of them.

Library affected

unsure/all/other

Reproduction

No response

Steps to reproduce

• Create a table with a column typed INTERVAL (nullable)
• Run supabase gen types --lang=typescript --local --schema > database.ts
• See that the column is inferred as string instead of string | null

System Info

System:
    OS: macOS 26.1
    CPU: (8) arm64 Apple M3
    Memory: 344.05 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.20.0
    npm: 11.6.2
    Watchman: 2025.10.27.00
  Browsers:
    Chrome: 142.0.7444.162
    Edge: 142.0.3595.80
    Safari: 26.1

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Supabase JS Library issue and not an issue with the Supabase platform. If it's a Supabase platform related bug, it should likely be reported to supabase/supabase instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.