-
-
Notifications
You must be signed in to change notification settings - Fork 414
Description
Please keep communication in ENGLISH to reach more contributors.
Is your feature request related to a problem? Please describe.
I often need to use DBGate while stepping through the code with a debugger, in order to troubleshoot persistence problems.
However, most of the time the code is running inside a transaction, meaning that changes won't be made visible for other connections until the end once it's committed, so DBGate shows outdated rows.
Describe the solution you'd like
It would be great to have an "isolation level" selector in the "table data" view and in "query" / "script" tabs. This would allow selecting one of the isolation levels supported by the DB engine.
Describe alternatives you've considered
Currently, I'm using SQL queries directly and adding the following line before each select:
set transaction isolation level read uncommitted;