Manual transaction - why have to do commit after select command ?

[zakjar]

I dislike the behavior of DBeaver in manual transaction mode.

I need to operate in manual transaction control mode, but there's no reason to perform a commit after only select commands.

I am accustomed to using Oracle's SQL Developer or PL/SQL Developer from Allround Automations, and neither environment requires me to commit after performing a simple select.

select user from dual -- why I have to do commit ???

Or any other select command.

There's no reason to commit when I'm just reading data and am in Read Committed mode.

Additionally, this behavior causes my PC's CPU to hit 100% utilization (I have filed a bug report regarding this).

Is there a way to configure DBeaver so that it remains in manual transaction mode but doesn't prompt for a commit when executing select commands? Or is there a way to control how long it takes before the commit prompt window appears?

[E1izabeth]

Even select queries may lead to data modification, for example, if you call a procedure that has modifying statements or you have a trigger.
Please take a look at the Smart commit mode https://github.com/dbeaver/dbeaver/wiki/Auto-and-Manual-Commit-Modes#smart-commit-mode Maybe it will satisfy your needs