-
Notifications
You must be signed in to change notification settings - Fork 4.1k
ui: Transactions page shows TXN TYPE as explicit even for implicit transactions #59210
Copy link
Copy link
Closed
cockroachdb/ui
#294Labels
A-webui-generalIssues on the DB Console that span multiple areas or don't have another clear category.Issues on the DB Console that span multiple areas or don't have another clear category.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Description
The Transactions page in the 20.2 DB console shows implicit transactions as explicit in the Transaction Details page.
This is an example of a transaction that was issued as an implicit transaction. Rollback statements used just to illustrate that an explicit transaction was not in progress.
root@snow:26257/defaultdb> rollback;
ERROR: there is no transaction in progress
root@snow:26257/defaultdb> insert into foo values (5);
INSERT 1
Time: 5ms total (execution 5ms / network 1ms)
root@snow:26257/defaultdb> rollback;
ERROR: there is no transaction in progress
root@snow:26257/defaultdb>
Repro:
- Start a single node
- Issue a simple implicit statement
- View the Transactions page in the DB Console
- View the Transaction Details page for the transaction
- Notice the statement is listed as Explicit
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-webui-generalIssues on the DB Console that span multiple areas or don't have another clear category.Issues on the DB Console that span multiple areas or don't have another clear category.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
