I have had the same thoughts about this inconsistency in comparison to e.g. PgAdmin III. Also, this "Save" button only appears when editing cell values defined as text, but not when editing numeric values, which does not opens this editing dialog. This, too, is inconsistent.
When I started using pdAdmin 4, I was confused by this need to double-save and even though I have used it for some months now, I haven't gotten used to this requirement. I guess that it's implemented like this, since the persistency/table refresh action (involves showing screen overlay with a throbber) isn't that fast and multiple persistency/table refresh actions triggered by editing and persisting data as pgAdmin III does would involve alot of screen flickering and a rather bad user experience.
If I select view/edit data and edit a field, I am presented with a dialog "Cancel or Save". However, if I click Save the data is NOT saved unless I close the table and again select "Save" rather than "Cancel" or "Don't Save". Leaving the table open and selecting another row does not update the data as is true with many other DB GUI tools. "Refresh" does not update the data either. I must click "Save" in two different dialogs for the data to be saved.
With the dialogue Save, the data will be temporarily saved into the grid itself, to save the data into the table permanently after all the modifications, click the Save button at the upper left corner in the toolbar.
This inconsistency is confusing, and means I must expend several more mouse clicks to know that my data has in fact been updated and to be able to view the table contents again. Testing or working on a large project, this adds up to a lot of time. It would be nice to be able to edit a field, then immediately run a query or function in some other window and know that the updated value would be used.
Is there a setting somewhere that will allow me to indicate that "Save means Save", or would this be a feature request / bug report?
AboutBox / Version Info screenshot attached
