Trino

Trino Driver

Use the Trino driver when your SQL endpoint is backed by Trino and you want catalog and schema browsing directly inside VS Code.

Default connection fields

Field	Default	Description
Host	Required	Trino coordinator or gateway hostname
Port	8080	Use 8443 or your HTTPS port when required by your deployment
Catalog	Optional but recommended	Default catalog for the session
Schema	Optional	Default schema inside that catalog
User	Optional	User name sent to Trino
SSL / HTTPS	false	Turn on for HTTPS endpoints
Verify HTTPS / SSL certificate	true	Turn off only for trusted dev endpoints
Timeout	Inherits global default	Per-connection timeout override in seconds

Trino-specific advanced fields

Field	Description
Headers	One key=value pair per line for auth proxies or custom routing headers
Session properties	One key=value pair per line for Trino session settings

DBeagle stores Trino headers in VS Code SecretStorage rather than keeping them in plain-text settings.

Common setup patterns

Standard username and password

Enter the host, port, catalog, schema, user, and password in the form and test the connection.

HTTPS endpoint

Turn on Use HTTPS / SSL. Keep certificate verification on unless you are connecting to a known local or development endpoint with a self-signed cert.

Proxy or bearer-token auth

Put proxy headers in the Headers box, for example:

Authorization=Bearer <token>
X-Trino-User=analytics

Session tuning

Put Trino session properties in the Session properties box:

query_max_execution_time=10m
exchange_compression=true

How Trino appears in DBeagle

Trino maps directly to DBeagle’s shared metadata model:

• catalog
• schema
• table or view
• column

That makes Trino one of the cleanest browsing experiences in the Connections tree.