Enable SQL format export in SQL Command editor

• Title.

Personally I think it would be productive to integrate adminer and local sql scripts execution.

This may appear out of nowhere, but I am available to fulfill any request in order to it be approved.

Thanks!!

Also, I created a .devcontainer in another branch to help environment setup and development for everyone; please see the sample branch https://github.com/srjheam/adminer/tree/srjheam/save-query-w-devcontainer .

In order to test this PR:

• Install and configure Docker Desktop for your operating system;
• Install VS Code and the Dev Containers extension;
• In VS Code, clone the fork and change to the branch containing the dev container and changes (https://github.com/srjheam/adminer/tree/srjheam/save-query-w-devcontainer);
• Use the Dev Containers: Reopen in Container command from the Command Palette;
• When VS Code restarts, all dependencies will be installed automatically in the dev container. After that you can open a browser window and access the webapp at http://localhost:8000/adminer/;
• Then, authenticate with the credentials that follow:

System: SQLite
Server: localhost
Username: root
Password: YOUR_PASSWORD_HERE
Database: /workspaces/adminer/my_database.db

• The proposed changes can be seen when you access the SQL Command page and run a query/statement;

• Result file (format = SQL, name convention = 'sql-cmd_YmdHis.sql', e.g. sql-cmd_20250521165519.sql

• Close the window to stop the container;

I've included some changes from @rlaiola .

If the commit messages do not follow the project convention, please do not hesitate to squash merge this PR, or contact me in order to restructure the git tree.

Also, as I discussed with @rlaiola on srjheam#2 (comment) , my devcontainers branch is just a sample and I would be more than happy to contribute with adminer in another PR with devcontainer environment setup.

@srjheam well done!

I think that another PR with just the dev container has the potential to streamline the development process.

Cheers.

I'm not interested in this feature as I see it confusing. I would expect the SQL export to give me SQL commands to recreate the data in another database, not just save the current commands to a file (which could be done be a simple copy/paste).

You can create a separate pull-request for .devcontainer although MySQL/MariaDB is the primary database for Adminer, not SQLite.

I'm not interested in this feature as I see it confusing. I would expect the SQL export to give me SQL commands to recreate the data in another database, not just save the current commands to a file (which could be done be a simple copy/paste).

Hi @vrana,

avoid the "copy & paste to save the query in a file" is exactly the goal of this PR. Let me give you some context: in my database courses students use Adminer to run their queries and then save/export the queries (NOT the inserts) to send for correction.

Important to say that queries are independent of the instance of the database. If not mistaken, the main goal of the "SQL command" page is to run queries (and why not saving them for use later on?). If one wants to export the database there is already an specific link for that (Export on the left side).

Cheers

You can create a separate pull-request for .devcontainer although MySQL/MariaDB is the primary database for Adminer, not SQLite.

Ok! Expect me doing so in the next few days.

The .devcontainer is agnostic to any databases and SQLite was just part of the sample I wanted to easily spin up for @rlaiola .

I'll create a new PR and make sure to support MySQL/PostgreSQL.

I'm not interested in this feature as I see it confusing. I would expect the SQL export to give me SQL commands to recreate the data in another database, not just save the current commands to a file (which could be done be a simple copy/paste).

In order to avoid the copy/paste/echo/touch flow to export the query, do you think it would be useful for the project to move this proposed feature from the export button to a new actual button in the interface with "Save query" label?

I'm not interested in this feature as I see it confusing. I would expect the SQL export to give me SQL commands to recreate the data in another database, not just save the current commands to a file (which could be done be a simple copy/paste).

In order to avoid the copy/paste/echo/touch flow to export the query, do you think it would be useful for the project to move this proposed feature from the export button to a new actual button in the interface with "Save query" label?

@srjheam perhaps, moving this feature under the 'History' link (below the textarea input and sideways to the 'Edit' link) could be an interesting alternative. This way I guess it becomes "less" confusing ('Edit' means edit the statement in the textarea, and 'Save' would indicate that the past statement that would actually be saved).

You can create a separate pull-request for .devcontainer although MySQL/MariaDB is the primary database for Adminer, not SQLite.

Ok! Expect me doing so in the next few days.

The .devcontainer is agnostic to any databases and SQLite was just part of the sample I wanted to easily spin up for @rlaiola .

I'll create a new PR and make sure to support MySQL/PostgreSQL.

@srjheam an alternative is to refer to a docker-compose file in the devcontainer (an Adminer container and a MySQL one). Here is an example that could help.

https://github.com/rtmonteiro/boca-playwright/tree/main/.devcontainer

@vrana what do you think of the save feature as in the image?