Feature Request : Add Auto Commit ON/OFF Toggle in DBCode UI

[devpkr1]

Hi Mike,

I’d like to request the addition of an Auto Commit ON/OFF feature in the database interface to better control transactions. This functionality is crucial, especially in production environments and testing scenarios, as it helps manage DML operations effectively and provides the ability to roll back changes when needed.

While I’m aware that TCL commands in SQL can control transactions, having an option to toggle Auto Commit directly from the UI—either through the connection settings or a button in the notebook/editor header—would greatly enhance usability. This would allow users to quickly enable or disable Auto Commit without manually running SQL commands.

Feature Request:

• Add an Auto Commit toggle in the connection settings or as a button in the notebook/editor header.
• Provide a visual indicator to show the current mode (ON/OFF).

Let me know if this can be considered for implementation. Looking forward to your thoughts!

Thanks

[dstockhammer]

For reference, this is DataGrip:

[mikeburgh]

My hold up on this is I need to re work how connections are assigned to the editor and notebooks.. well that's been my assumption..

Do you only expect the auto commit option to effect the SQL you are writing (in the editor/notebook) vs say when you edit a table or run a SQL file ? That's been my assumption.. basically that if you edit data in a table, use the UI to alter a table/drop one etc then all that is auto committed.. but any SQL you write in the editor is controlled by that option ?

Assuming that's how you are seeing things, just working through how I go about doing that in an efficient manner, and ensure it stays isolated..

[devpkr1]

Yes, exactly — that’s how I’ve been thinking about it too.

The auto-commit option should only apply to SQL executed in the editor or notebooks, where users are explicitly writing queries and may want transactional control. For UI-driven actions like editing table data, altering schemas, or dropping tables, I’d fully expect those to be auto-committed by default — they’re typically one-off changes and shouldn't be tied to the editor’s transaction mode.

So your assumption makes perfect sense — the key is making sure the connection behavior for the editor/notebook is isolated from the rest of the app. That way, toggling auto-commit doesn’t unintentionally affect other workflows.

[mikeburgh]

I have just released a first look at this in version 1.17.31.. it's only enabled for Postgres, and the docs for it are here: https://dbcode.io/docs/query/transaction-control

I will see how it goes, and any issues, then look at enabling it for the other drivers that support transactions.

[mikeburgh]

I have rolled this out to the remaining db's that support it in 1.17.37 which has been released. Going to close this and will track any problems in new issues.