Sabiql: A driver-less TUI for Postgres and SQLite
ToolsComments
If the tool relies on those config files, would a user potentially encounter conflicting behavior if the TUI overrides a setting defined in the .psqlrc? I wonder how it handles priority between its own UI state and the underlying CLI config.
I'm wondering about that dependency on host binaries... if the user has a different version of psql than the tool expects, will it just crash or behave weirdly? That seems like a tricky edge case...
This approach assumes the target environment is a developer machine. In containerized CI/CD or locked-down production shells, requiring the full CLI toolchain is often a non-starter.
same issue as pgcli
Native drivers are a maintenance nightmare. Most modern DB clients spend more time fighting connection string edge cases than actually displaying data. Wrapping the CLI is the only way to stay sane.
The real advantage here is the preservation of the .psqlrc and .sqliterc configurations. Native drivers typically ignore these user-level environment settings, which forces a redundant reconfiguration of the session.