Allow naming a saved SQL entry during the initial save

[openai0229]

Chat2DB Edition

Chat2DB Community

User Problem

When a SQL console is saved for the first time, Chat2DB persists it with the current workspace or database-derived title. The user cannot enter a meaningful name during the save action, so saved SQL entries are difficult to identify until they are renamed separately.

Concrete Use Case

An engineer prepares several maintenance queries for the same database. When saving each query, they need to assign names such as Check replication lag or Archive expired orders before the entries appear in the saved SQL list.

Product Area

SQL editor

Proposed Outcome

The first manual save of a SQL console should request a name, prefilled with a sensible default. Confirming should save the SQL under that name, while cancelling should leave it unsaved. Later saves should continue updating the same saved record without prompting again.

Alternatives Considered

Save with the generated title, find the entry in the saved SQL list, and rename it afterward. This adds an avoidable second step and is error-prone when several entries have similar generated names.

Contribution

I can provide product feedback

Submission Checklist

• I searched existing issues and Discussions for duplicates.
• I selected the affected Chat2DB edition.

[github-actions]

Thanks for the clear feature request. The requested flow is to prompt for a name, prefilled with a sensible default, on the first manual save of a SQL console; confirming creates the saved SQL entry under that name, while cancelling leaves it unsaved.

The report is complete for maintainer review. Subsequent saves should update the same saved record without prompting again.

Generated by AI Issue Assistant for #2235 · 6.42 AIC · ⌖ 2.73 AIC · ⊞ 16.2K · ◷