DBeaver
Replies: 2 comments
-
|
Such indication is intentional to show that work in SQL editor is not finished. If DBeaver consider that transaction is opened depends on the transaction mode you use. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
When the SQL Editor thinks that there are Uncommitted transactions, it will always show the file as Unsaved (no matter how many times you try to save the file). Also I do not know why I have Uncommitted transactions if all what I ran were SELECT statements. It appears as if DBeaver considers OPEN CURSORS also as UNCOMMITTED TRANSACTIONS?
DBeaver Version
Version 23.0.2.202304091457
Operating System
No response
Database and driver
No response
Steps to reproduce
No response
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions