Thread: No commit nor Rollback button

No commit nor Rollback button

From

legrand legrand

Date:

15 October 2017, 01:14:49

Hello,

Most of RDBMS users don't want to use autocommit mode expecting to have a
change to Rollback in case of problem.

Most of database GUI have Commit/ Rollback buttons (greyed in autocommit
mode, enabled in non autocommit mode).

Is there a chance to see thoses buttons (using preferences or other) ?

Regards
PAscal




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

Melvin Davidson

Date:

15 October 2017, 04:30:52

Please note, I am not PgAdmin4 support.

However, it seems to me that what you want is handled in 
File
  Preferences
    SQL Editor
        Options
            Auto commit?    True/False 
            Auto rollback?  True/False 

Melvin Davidson 🎸
I reserve the right to fantasize.  Whether or not you 
wish to share my fantasy is entirely up to you. 
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day 
www.folkalley.com



 On Saturday, October 14, 2017, 3:22:16 PM EDT, legrand legrand <legrand_legrand@hotmail.com> wrote: 


Hello,

Most of RDBMS users don't want to use autocommit mode expecting to have a
change to Rollback in case of problem.

Most of database GUI have Commit/ Rollback buttons (greyed in autocommit
mode, enabled in non autocommit mode).

Is there a chance to see thoses buttons (using preferences or other) ?

Regards
PAscal




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

dangal

Date:

15 October 2017, 08:41:18

I think like you, you should have two buttons, commit and rollback



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

Dave Page

Date:

16 October 2017, 13:53:39

On Sat, Oct 14, 2017 at 8:14 PM, legrand legrand <legrand_legrand@hotmail.com> wrote:

Hello,

Most of RDBMS users don't want to use autocommit mode expecting to have a
change to Rollback in case of problem.

Most of database GUI have Commit/ Rollback buttons (greyed in autocommit
mode, enabled in non autocommit mode).

pgAdmin hasn't had commit/rollback buttons in nearly 20 years, and there have been very few requests to add them in that time. Would the extra space on the button bar really be worth it for most users given so few have ever asked for it?

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: No commit nor Rollback button

From

dangal

Date:

16 October 2017, 19:07:46

for me it would be necessary, if possible
thanks a lot



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

legrand legrand

Date:

16 October 2017, 23:46:39

Maybe after 20 years,
it is time to switch tool default from autocommit to commit/rollback ...

to have a chance to be compared with Oracle SQL developer or others

PAscal
SQLeo projet manager



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

Melvin Davidson

Date:

17 October 2017, 00:16:15

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;


Melvin Davidson 🎸
I reserve the right to fantasize.  Whether or not you 
wish to share my fantasy is entirely up to you. 
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day 
www.folkalley.com



 On Monday, October 16, 2017, 1:51:35 PM EDT, legrand legrand <legrand_legrand@hotmail.com> wrote: 


Maybe after 20 years,
it is time to switch tool default from autocommit to commit/rollback ...

to have a chance to be compared with Oracle SQL developer or others

PAscal
SQLeo projet manager



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

"David G. Johnston"

Date:

17 October 2017, 00:30:18

On Mon, Oct 16, 2017 at 11:16 AM, Melvin Davidson <melvin6925@yahoo.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.

Re: No commit nor Rollback button

From

Michael Rasmussen

Date:

17 October 2017, 01:16:00

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.

Michael Rasmussen

Sr. Data Engineer

Porch

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

On Mon, Oct 16, 2017 at 11:16 AM, Melvin Davidson <melvin6925@yahoo.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;

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.

Re: No commit nor Rollback button

From

Murtuza Zabuawala

Date:

17 October 2017, 01:36:29

pgAdmin4 also has option in tool menu.

If Auto commit? and Auto rollback? is set to true then basically it is Auto mode And If you prefer manual control over transactions then just uncheck both the options that will be Manual mode.

Regards,

Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

On Tue, Oct 17, 2017 at 12:46 AM, Michael Rasmussen <michaelr@porch.com> wrote:

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.

--
Michael Rasmussen
Sr. Data Engineer
Porch

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

On Mon, Oct 16, 2017 at 11:16 AM, Melvin Davidson <melvin6925@yahoo.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.

Re: No commit nor Rollback button

From

legrand legrand

Date:

17 October 2017, 02:33:54

Hi Murtuza,

I found those options for switching between autocommit mode and manual mode.

What I suggest here is to add one button for commit and one button for
rollback, 
they would be green and red in manual transaction mode 
they would be greyed in autocommit mode.

A more advanced behavior in manual mode, is to let them greyed as long as
there is no modification done in the transaction.

Regards
PAscal



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

Murtuza Zabuawala

Date:

17 October 2017, 11:26:02

On Tue, Oct 17, 2017 at 2:03 AM, legrand legrand <legrand_legrand@hotmail.com> wrote:

Hi Murtuza,

I found those options for switching between autocommit mode and manual mode.

What I suggest here is to add one button for commit and one button for
rollback,
they would be green and red in manual transaction mode
they would be greyed in autocommit mode.

A more advanced behavior in manual mode, is to let them greyed as long as
there is no modification done in the transaction.

Oh okay, that functionality is not available.

In my personal opinion, I don't see requested buttons for commit/rollback as frequently used feature by most user when you have auto commit/rollback mode available.

Regards
PAscal

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

Dave Page

Date:

17 October 2017, 14:07:26

On Tue, Oct 17, 2017 at 6:26 AM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote:

On Tue, Oct 17, 2017 at 2:03 AM, legrand legrand <legrand_legrand@hotmail.com> wrote:
Hi Murtuza,

I found those options for switching between autocommit mode and manual mode.

What I suggest here is to add one button for commit and one button for
rollback,
they would be green and red in manual transaction mode
they would be greyed in autocommit mode.

A more advanced behavior in manual mode, is to let them greyed as long as
there is no modification done in the transaction.
Oh okay, that functionality is not available.

In my personal opinion, I don't see requested buttons for commit/rollback as frequently used feature by most user when you have auto commit/rollback mode available.

I agree - and based on the lack of requests over the years, I believe most users would too.

I can see why for some people who choose to turn auto-commit/auto-rollback off they may be useful, however we cannot simply add new features every time someone asks for something. Doing so adds maintenance costs, and increases complexity of the UI for *everyone*. That is part of the reason why pgAdmin III became unmaintainable; we added too many features on a whim without giving enough thought to whether or not the added code and UI complexity was justified, and eventually ended up with a mess of spaghetti-code.

Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: No commit nor Rollback button

From

"David G. Johnston"

Date:

17 October 2017, 20:03:58

On Tue, Oct 17, 2017 at 1:07 AM, Dave Page <dpage@pgadmin.org> wrote:

I can see why for some people who choose to turn auto-commit/auto-rollback off they may be useful, however we cannot simply add new features every time someone asks for something. Doing so adds maintenance costs, and increases complexity of the UI for *everyone*. That is part of the reason why pgAdmin III became unmaintainable; we added too many features on a whim without giving enough thought to whether or not the added code and UI complexity was justified, and eventually ended up with a mess of spaghetti-code.

So consider the lack of requests to be not so lacking anymore...

One concrete advantage to the buttons, and mind you I haven't actually used pgAdmin4 but do use a GUI, is that in my GUI if you were to send the COMMIT command to the server as text any and all result set tables that are present on the current screen are removed the a new command result for the commit response replaces them. If one uses the button the result tables are left alone.

Frankly, auto-commit mode can be dangerous so if you are advocating that people simply use that and forget about manually committing altogether I think you are misguided in your thinking. In the UI that I use if I send a "begin" to the server then, and only then, do the commit/rollback buttons appear (and auto-commit is disabled temporarily). With that flow your "end-user UI complexity" argument becomes significantly more specious and you are just left with "code complexity".

David J.

Re: No commit nor Rollback button

From

Francis Fish

Date:

18 October 2017, 14:46:15

Regardless of the button or not to button some visual indicator of commit/rollback status that doesn't mean diving into menus would probably help, e.g. a red dot somewhere in a window's decoration meaning that window will auto commit.

I come originally from an Oracle background too and remember being extremely surprised that transactions were off by default in both PG and MySQL.

Despite that, I use PGAdmin for development. I don't let GUIs with magic buttons anywhere near production databases. They are always managed through scripts. So it may have surprised me, but it didn't bother me, if you see what I mean.

Thanks and Regards,

Francis

07764 225 942

Pharmarketeer is a registered company in England and Wales 06940361, registered office 64 Westbank Road, Birkenhead, Merseyside, CH42 7JP

"So when targets seem stupid, arbitrary and unfair it's because they are. The only way to improve is to look at the whole system people are operating with, the basic tools, their training, how much initiative they are allowed, are you measuring the right things (more about that later) and then you can improve. But it's the system you improve, not the people you beat into performing even worse." Unicorns in the mist

CV http://www.pharmarketeer.com/francis.html

Lean Teams Consultancy

On Tue, Oct 17, 2017 at 3:03 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:

On Tue, Oct 17, 2017 at 1:07 AM, Dave Page <dpage@pgadmin.org> wrote:
I can see why for some people who choose to turn auto-commit/auto-rollback off they may be useful, however we cannot simply add new features every time someone asks for something. Doing so adds maintenance costs, and increases complexity of the UI for *everyone*. That is part of the reason why pgAdmin III became unmaintainable; we added too many features on a whim without giving enough thought to whether or not the added code and UI complexity was justified, and eventually ended up with a mess of spaghetti-code.

So consider the lack of requests to be not so lacking anymore...

One concrete advantage to the buttons, and mind you I haven't actually used pgAdmin4 but do use a GUI, is that in my GUI if you were to send the COMMIT command to the server as text any and all result set tables that are present on the current screen are removed the a new command result for the commit response replaces them. If one uses the button the result tables are left alone.

Frankly, auto-commit mode can be dangerous so if you are advocating that people simply use that and forget about manually committing altogether I think you are misguided in your thinking. In the UI that I use if I send a "begin" to the server then, and only then, do the commit/rollback buttons appear (and auto-commit is disabled temporarily). With that flow your "end-user UI complexity" argument becomes significantly more specious and you are just left with "code complexity".

David J.

Re: No commit nor Rollback button

From

dangal

Date:

20 October 2017, 04:58:56

Actually to manage a production environment I do not understand how someone
can use the auto commit.
In most Oracle database management tools, they all have the commit and
rollback buttons.
I do not think it's so complicated to add and it complicates your
maintenance a lot
I do not want to minimize the work of the developer and maintains



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html

Re: No commit nor Rollback button

From

Vano Beridze

Date:

04 November 2017, 23:34:30

I also come from Oracle and all tools have autocommit disabled by default.

It's more natural to make sure that everything went well and only after 
that commit the transaction.

Sometimes you realize that you made a huge mistake. Rollback is your friend.

Vano Beridze
Software Developer
Silk Road Group

On 10/20/2017 2:58 AM, dangal wrote:
> Actually to manage a production environment I do not understand how someone
> can use the auto commit.
> In most Oracle database management tools, they all have the commit and
> rollback buttons.
> I do not think it's so complicated to add and it complicates your
> maintenance a lot
> I do not want to minimize the work of the developer and maintains
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html
>
>
>