Feature request: Support query files per connection

[huantrinh1802]

Problem / Motivation

Currently, the SQL TUI supports:

• An interactive query editor per connection
• Saved queries per connection

However, there is no way to associate query files (e.g. .sql files) with a specific connection. This makes it harder to reuse and manage common or complex queries across sessions.

Proposed feature

Add support for query files per connection, allowing users to:

• Attach one or more .sql files to a connection
• Organize reusable/common queries alongside the connection definition
• Open and run these files directly from the TUI without copy-pasting into the editor

Use cases

• Storing commonly used reports or diagnostic queries for a specific database
• Keeping complex queries under version control
• Sharing standard queries across teams
• Reducing duplication between “saved queries” and external SQL files

Possible approaches (suggestions, not requirements)

• A configurable directory per connection for SQL files
• Automatic discovery of .sql files in a connection-specific folder
• A TUI panel or menu to browse and execute query files

Benefits

• Better workflow for power users
• Improved query reuse and maintainability

Happy to help with design discussion or testing if this feature is considered 🙂

[Maxteabag]

I would like to do this. I have already shifted history from JSON to individual .sql files, but I realize this isn't doing full justice to the request. I need some time to think about a good solution here.