transaction autostart and autocommit
Section in options for transaction adjusting: autostart, isolation level and so on.
Илья Масков commented
It took 8 years, wow. Thank you!
Rhys Bevilaqua commented
The new version (4.0.237) now has transaction autostart but no option to disable it, while i appreciate the use of this feature we need options to be able to have auto commit.
Being able to take locks on tables and cause application timeouts is a serious side effect of taking out these transactions, and it's very easy to forget to commit or rollback them.
Please add the options for disable the autocommit feature by default!
It is a very basic feature that other SQL IDE had.
+1 I was about to buy several licenses since i've found out that this option is not available. Will be very dangerous for our dev team that is used to have that in TOAD/SqlDeveloper.
I've just went several times back and forth through all the settings and was not able to find how to turn autocommit off. I could not believe it's not there and then I found this feature request. Very basic feature and easy to implement, top-rated and more than 5 years old!!! Probably time to get back to SQL Developer.
Steve P commented
+1 This is very important, especially coming from SQL Developer. Important enough that I probably won't be purchasing this for my team unfortunately.
Must-have feature. I even consider going back to SQL Developer cause it's so dangerous, at least for deployment/migration scripts
please ! +1
Greg A commented
Yeah, this is very, very necessary.
Anton Wazin commented
This is a must-have feature for serious database development with complex schemas.
Default auto-commit and the manual "transaction setting" is very error prone.
This makes DB forge to no 1 frustrating DB development tool in our team. :-/
if you introduce a ways to disable autocommits (like toad there should be explicit commit) I am looking to buy at least 25 licenses
autocommit should be switched off by default because it is very dangerous if you are working in a productive environment.
Auto-commit is dangerous. Needing to remember to start a transaction before any update is also dangerous. These should be treated like any other IDE -- you have to manually commit a change. I don't feel comfortable using this IDE with how transactions are currently handled.
Vincent Harcq commented
Autocommit should be switched off by default
Then configurable at Global Option, then by DB connexion
+1. This would be a good addition to the product.
AdminDevart (_, Devart) commented
Display the state of the transaction in the status bar of the document
Дмитрий Ларионов commented
i don't understand what happens in dbForge Studio for Oracle now. I press 'Begin Transaction' buttion, then do my INSERTs and see (in othen application), that records are appeared immediately.
By searching in Internet, i found that autocommit may be set only at application level (no autocommit at server side of Oracle). But i see no options in dbForge Studio for autocommit.
It is also impossible to get my current transation isolation level at Oracle. I feel myself unsecure.
Must be able to turn off auto-commit. Transaction usage should be automatic, not requiring a button click.