[Bug]: Error on Visual Query when "user" table is used (Postgres)

[brAvEiitoOr]

Describe the bug

On a Visual Query, when I put a table named "user" and execute it, the interface shows an error indicating that the column does not exist. It happens on a Postgres connection.

Probably because tabularis runs the query as SELECT user... instead of SELECT "user"...

To Reproduce

1. Connect to a Postgres database with a "user" table
2. Open a New Visual Query
3. Drag the "user" table to the space
4. Select a column
5. Run the query

OS Version

CachyOS

Tabularis Version

v0.13.2

Relevant Log Output

[DhruvShah-Dev]

Opened PR #553: #553

The Visual Query Builder now passes the active driver into SQL generation and quotes generated PostgreSQL identifiers when needed, including reserved table or column names such as user and order.

Validation completed:

• pnpm.cmd vitest run tests/utils/visualQuery.test.ts
• pnpm.cmd typecheck
• pnpm.cmd lint
• pnpm.cmd build
• git diff --check
• pnpm.cmd exec gitnexus detect-changes

[aesslinger]

Re-verified this on main with a live repro — confirmed fixed.

Test setup: Local Postgres 16 instance with a user table (id, username, email — matching the repro steps). Ran the app's actual generateVisualQuerySQL() (Visual Query Builder's SQL generator) using the real capabilities payload published by the live postgresql plugin (identifier_quote: "\"", sql_dialect: "postgres").

• Generated SQL: FROM "user" t1 — correctly quoted.
• Executed against the live user table → succeeded, rows returned.
• For contrast, ran the unquoted form (FROM user t1) against the same table → reproduced the original error verbatim: ERROR: column t1.id does not exist.

History for context:

• Fix PostgreSQL visual query identifier quoting #553 (merged, aeb11fd2) — original fix, added identifier quoting to the Visual Query Builder.
• Hardcoded driver === "postgres" checks in core break the standalone PostgreSQL plugin #614 — regression found afterward: the standalone plugin runs under driver id "postgresql", not the builtin "postgres", so id-string-keyed quoting checks still missed it for plugin connections.
• c9a38fbd ("fix: identifier quoting keys off dialect, not driver id (Hardcoded driver === "postgres" checks in core break the standalone PostgreSQL plugin #614)"), part of feat: PostgreSQL plugin reaches parity + safety with built-in driver (#614) #577 — made shouldQuoteIdentifiers read capabilities.sql_dialect instead of comparing driver-id strings, closing that gap.

Current main handles both the builtin driver and the standalone plugin correctly. No further code changes needed on this one — flagging for @debba / @NewtTheWolf to confirm and close.