DROP CONNECTION

Removes a connection registration. External tables registered through this connection must be dropped or relocated first.

Category: configurationPrivilege: adminDeltaForge extension

Syntax

DROP CONNECTION [IF EXISTS] <name>

Description

## Overview DROP CONNECTION removes the external_connections row. The credential or credential-storage references are not cascaded; the vault entries and backends those ids point to are left in place. ## Behavior - The HTTP adapter calls DELETE /connections/{name}. Without IF EXISTS, a 404 raises an error; with IF EXISTS, returns false. - External-table registrations that resolve through this connection become unreadable after DROP. They are not automatically removed; list via catalog queries and drop or reregister first. - The credential and credential-storage references are not cascaded. The vault entries and backends those ids pointed to are unaffected. ## Access Control Requires the admin role. The Control Plane enforces connections:write on DELETE /connections/{name}. ## Compatibility DeltaForge extension.

Parameters

Name	Type	Description
`name`		Specifies the name of the connection.
`if_exists`		When true, a missing connection is a clean no-op.

Examples

-- Drop an unused connection
DROP CONNECTION old_pg;

-- Idempotent cleanup
DROP CONNECTION IF EXISTS scratch_conn;

Pitfalls

DROP does not cascade to external tables registered through this connection. Those tables become unreadable at query time. List external tables via list_external_tables_by_connection before dropping.
DROP does not rotate or drop the referenced vault entries or CREDENTIAL STORAGE backends. Those live independently and must be cleaned up separately if no longer needed.
There is no DROP ... CASCADE variant in v1.