SQL Client for PostgreSQL in VS Code
PostgreSQL client for VS Code. Connect to PostgreSQL or Supabase, browse schemas and run SQL queries with Nexo SQL Studio's free worksheets and results.
Before connecting
Enter the PostgreSQL database name and role. Check schema permissions and TLS requirements. For Supabase, use the direct or pooler details provided by the project; IPv4/IPv6 reachability and pooler behavior can affect your workflow.
Run your first query
SELECT current_database(), current_user;Troubleshooting
Check the selected engine, host or file path, database name, account permissions and TLS requirements. Keep the connection editor open while correcting failed tests. Include the engine, server version, extension version and a sanitized error when requesting support; never include passwords or wallet secrets.
Hosted databases: use the engine's connection settings. Supabase uses PostgreSQL; Oracle Cloud and Autonomous Database use Oracle. Poolers, wallets, authentication and provider-specific services need their own configuration and compatibility checks.
Supported databases
Feature availability
Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.
Supported databases
Feature availability
Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.
Oracle Database, PostgreSQL, MySQL, MariaDB, SQLite, Microsoft SQL Server. Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.
Yes. Nexo supports six database engines and retains dedicated advanced Oracle tooling, including Oracle connection settings and SQL/PLSQL development workflows.
Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.
Free covers core SQL workflows. Pro adds advanced development, delivery and AI/MCP tools. A Pro license does not make an unsupported engine feature available.
Yes. Select the corresponding engine when creating a connection. SQLite uses a local file; server databases use their connection details. Consult the engine guide for requirements and feature availability.
Hosted databases: use the engine's connection settings. Supabase uses PostgreSQL; Oracle Cloud and Autonomous Database use Oracle. Poolers, wallets, authentication and provider-specific services need their own configuration and compatibility checks.
Ordinary Oracle connections use the bundled Thin driver and do not require Oracle Instant Client. Thick-mode or external-authentication workflows may require additional Oracle client configuration.