Re: No commit nor Rollback button

DataGrip has transaction control in the tool menu. It is pretty handy to have that toggle at hand.

Yes, I know how to write a manual transaction, but the point of using a GUI tool is to speed things up and make my life as a Data Engineer easier. It is not for forcing me to type extraneous commands repeatedly.

[cid:image001(dot)png(at)01D34678(dot)872DEC70]

[cid:image002(dot)png(at)01D34678(dot)872DEC70]

--
Michael Rasmussen
Sr. Data Engineer
Porch

From: "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Date: Monday, October 16, 2017 at 11:30 AM
To: Melvin Davidson <melvin6925(at)yahoo(dot)com>
Cc: "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>, legrand legrand <legrand_legrand(at)hotmail(dot)com>
Subject: Re: No commit nor Rollback button

On Mon, Oct 16, 2017 at 11:16 AM, Melvin Davidson <melvin6925(at)yahoo(dot)com<mailto:melvin6925(at)yahoo(dot)com>> wrote:
You don't need buttons.

Just go to
File
Preferences
SQL Editor

and change Auto commit? to False
and Auto rollback? to False

Or whatever you prefer.
That is what those options are for!

Or learn how to use a TRANSACTION in PostgreSQL.
IE:
BEGIN;

​Personally, if I'm in a GUI I'd prefer buttons. They both allow one to quickly see whether they are in a transaction or not (by greying out the buttons when their use is not applicable) and provide a mouse user a very quick way to commit/rollback the query they just executed via clicking the "run query" button.

This has absolutely nothing to do with "Auto Commit/Rollback" other than the buttons would only be meaningful when said option is disabled.

​David J.