add rollback and commit action buttons on Query Tool (RM #2418)

[dpage]

Issue migrated from Redmine: https://redmine.postgresql.org/issues/2418 Originally created by Doris Lippert at 2017-05-17 16:49:24 UTC.

PGAdmin 3 had commit and rollback buttons. I used them all the time, leaving auto-commit and auto-rollback turned off. Oracle SQL Developer UI is a good example of how to manage commits and rollbacks in a way that is natural. PGAdmin3 was a bit clunky and PGAdmin4 is missing this feature.

Could also add keyboard shortcuts for the buttons.

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-1 Originally created by Vladimir Yavorksiy at 2018-04-27 08:29:30 UTC.

This is necessary tool! One year old issue and Autocommit feature is still useless. Can't use PGAdmin4 in production.

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-2 Originally created by Akshay Joshi at 2018-06-22 10:25:51 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Sprint changed		Ready

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-3 Originally created by Jos De Graeve at 2019-01-22 09:52:51 UTC.

Is there any update on this ?

This feature would be a very valuable enhancement for many users. When pgadmin is used to do ad-hoc queries on a server, best practice is not to use auto-commit.

There is already an indicator that shows if you're in a transaction, but no UI elements that allow to easily commit or rollback the transaction.

Thanks in advance.

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-4 Originally created by Akshay Joshi at 2019-01-31 07:41:41 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Relationship (duplicated) changed		RM #3775

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-5 Originally created by Vladimir Yavorksiy at 2019-02-07 14:55:12 UTC.

still wait

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-6 Originally created by Akshay Joshi at 2019-02-09 03:04:53 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Sprint changed	Ready	EDB Sprint 34

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-7 Originally created by Akshay Joshi at 2019-02-19 06:58:48 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Status changed	New	In Progress
Assigned To changed		Akshay Joshi

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-8 Originally created by Akshay Joshi at 2019-02-21 12:40:54 UTC.

Patch Sent: https://www.postgresql.org/message-id/CANxoLDfrYmvqJwNCmF7oZfmf4t+BUrBBy-B9k-CxwwOsWXCsJA@mail.gmail.com

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-9 Originally created by Dave Page at 2019-02-22 14:26:58 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Fixed Version changed		4.3

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-10 Originally created by Akshay Joshi at 2019-02-22 14:28:14 UTC.

Applied in changeset commit:38b034ec3c734090156ad97b10d555e752c7c3f7.

Redmine ticket header update:

Name	Old Value	New Value
Status changed	In Progress	In Testing
Done Ratio changed	0	90

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/2418#note-11 Originally created by Fahar Abbas at 2019-03-07 08:24:35 UTC.

This is already Resolved in latest pgAdmin4 4.3 Build.

Redmine ticket header update:

Name	Old Value	New Value
Status changed	In Testing	Resolved
Done Ratio changed	90	100

[dpage]

Issue closed on Redmine.