Re: No commit nor Rollback button

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
<https://leanpub.com/unicorns>

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

Lean Teams Consultancy <http://lean-teams.co.uk>

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

> On Tue, Oct 17, 2017 at 1:07 AM, Dave Page <dpage(at)pgadmin(dot)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.
>