Access an existing database connection directly via a link that opens the full-screen SQL editor #1022

New issue

Open

opened 2026-03-04 11:34:28 -05:00 by deekerman · 1 comment

deekerman commented

2026-03-04 11:34:28 -05:00

Owner

Originally created by @mnismael on GitHub (Oct 30, 2025).

Originally assigned to: @Wroud on GitHub.

Dear CloudBeaver Team,

I’m currently integrating CloudBeaver into an Angular application, using it primarily as a direct SQL editor. The goal is to provide users with a seamless experience where they can interact with the SQL editor without needing to manage connections or navigate through the default interface.

Current Use Case:

CloudBeaver is embedded in an Angular app.
Users access the SQL editor directly, bypassing connection setup.

Feature Request:
I would like to enable a smoother integration by establishing a session and redirecting users directly to the full-screen SQL editor (/#/sql-editor) via a single endpoint—similar to the behavior triggered by the “Open in Tab” action. Ideally, this endpoint would:

Automatically create a session.
Redirect directly to the SQL editor view
Bypass the default main view (which includes the sidebar with connections).

The endpoint would behave similarly to the existing /open one already offered. But instead of redirecting to the root URI, it would get the sessionId and redirectly automatically to the full screen editor

This would significantly improve the user experience and streamline the integration. I’m open to contributing development effort to implement this feature if it’s feasible within the current architecture.
Please let me know if this is something that can be considered or if there are any technical constraints I should be aware of.

Best regards,
Mohamad

Originally created by @mnismael on GitHub (Oct 30, 2025). Originally assigned to: @Wroud on GitHub. Dear CloudBeaver Team, I’m currently integrating CloudBeaver into an Angular application, using it primarily as a direct SQL editor. The goal is to provide users with a seamless experience where they can interact with the SQL editor without needing to manage connections or navigate through the default interface. **Current Use Case:** - CloudBeaver is embedded in an Angular app. - Users access the SQL editor directly, bypassing connection setup. **Feature Request:** I would like to enable a smoother integration by establishing a session and redirecting users directly to the full-screen SQL editor (/#/sql-editor) via a single endpoint—similar to the behavior triggered by the “Open in Tab” action. Ideally, this endpoint would: - Automatically create a session. - Redirect directly to the SQL editor view - Bypass the default main view (which includes the sidebar with connections). The endpoint would behave similarly to the existing [/open](https://github.com/dbeaver/cloudbeaver/wiki/Access-to-an-existing-database-connection-with-a-link) one already offered. But instead of redirecting to the root URI, it would get the sessionId and redirectly automatically to the full screen editor This would significantly improve the user experience and streamline the integration. I’m open to contributing development effort to implement this feature if it’s feasible within the current architecture. Please let me know if this is something that can be considered or if there are any technical constraints I should be aware of. Best regards, Mohamad

deekerman added the

xf:sql editor

wait for response

labels

2026-03-04 11:34:28 -05:00

deekerman commented

2026-03-04 11:34:37 -05:00

Author

Owner

@Wroud commented on GitHub (Nov 10, 2025):

Hello, unfortunately, we don't plan to improve this behaviour in the near future. A workaround might be to connect to the database first via GraphQL (initConnection) and then create a SQL context (sqlContextCreate). After that, you can use contextId to open the SQL Editor window: http://localhost/#/sql-editor/{contextId}

@Wroud commented on GitHub (Nov 10, 2025): Hello, unfortunately, we don't plan to improve this behaviour in the near future. A workaround might be to connect to the database first via GraphQL (`initConnection`) and then create a SQL context (`sqlContextCreate`). After that, you can use `contextId` to open the SQL Editor window: `http://localhost/#/sql-editor/{contextId}`