Обсуждение: pgadmin4 Edit and "Save" data

If I select view/edit data and edit a field, I am presented with a dialog "Cancel or Save". However, if I click Save
thedata is NOT saved unless I close the table and again select "Save" rather than "Cancel" or "Don't Save". Leaving the
tableopen and selecting another row does not update the data as is true with many other DB GUI tools.  "Refresh" does
notupdate the data either. I must click "Save" in two different dialogs for the data to be saved.
 

This inconsistency is confusing, and means I must expend several more mouse clicks to know that my data has in fact
beenupdated and to be able to view the table contents again. Testing or working on a large project, this adds up to a
lotof time. It would be nice to be able to edit a field, then immediately run a query or function in some other window
andknow 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

From Khushboo Vashi:

" to save the data into the table permanently after all the modifications, click the Save button at the upper left
cornerin the toolbar."
 

Ah! That button with the floppy disk icon (Grandpa, what's a floppy disk?), with the hover hint that says "save file"
(not"save data"). Thanks - I missed that!
 


>  -------Original Message-------
>  From: Janus <janus.e@gmail.com>
>  To: Dave Page <dpage@pgadmin.org>
>  Cc: Khushboo Vashi <khushboo.vashi@enterprisedb.com>, mickey@thesweetoasis.com, pgadmin-support lists.postgresql.org
<pgadmin-support@lists.postgresql.org>
>  Subject: Re: pgadmin4 Edit and "Save" data
>  Sent: 02 Apr '19 04:29
>  
>  Dave,
>  When you edit data in PgAdmin III and use the Tab-key to move focus to
>  next cell, it does not automatically update changes in cell values,
>  but when you press Enter-key to exit the edit-mode of a cell, the
>  changed value is submittet to the database immediately. This is easily
>  tested by refreshing the edited table after either mentioned
>  edit-exits; first results in a warning saying the table has changes,
>  the other simply refreshes the table and the changes made is reflected
>  in the reloaded table.
>  
>  Ok then, at least change the "Save" to "OK". But since you are going
>  to perform changes to the edit-box i pgAdmin 4, it would be really
>  nice if the edit-box could remember resizing changes made :) Or
>  alternatively have a minumum size and a maximum size and adapt the
>  size of the box relative to the length of the text that it presents,
>  although this does not cater for user preferences towards height/width
>  ratio.
>  
>  Best regards,
>  Janus
>  
>  On Tue, 2 Apr 2019 at 10:16, Dave Page <dpage@pgadmin.org> wrote:
>  
>  > On Tue, Apr 2, 2019 at 8:34 AM Janus <janus.e@gmail.com> wrote:
>  >
>  >> 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.
>  >
>  > pgAdmin 3 didn't work like that though. The only difference here is
>  > that text fields (and a few others such as JSON/JSONB) edit in a
>  > popup rather than directly in the grid. The reason for this is that
>  > it allows you to have more room to work - the popup can be expanded
>  > as needed to give editing room far more conveniently that a grid
>  > cell.
>  >
>  > The only change I'm inclined to make here is to change the Save
>  > button on the popup to say "OK" or similar to remove the implication
>  > that the data will actually be saved rather than just updated in the
>  > grid.
>  >
>  > On Tue, 2 Apr 2019 at 06:21, Khushboo Vashi
>  > <khushboo.vashi@enterprisedb.com> wrote:
>  >
>  > On Mon, Apr 1, 2019 at 11:53 PM <mickey@thesweetoasis.com> wrote:
>  > 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
>  
>  --
>  
>  Dave Page
>  Blog: http://pgsnake.blogspot.com
>  Twitter: @pgsnake
>  
>  EnterpriseDB UK: http://www.enterprisedb.com
>  The Enterprise PostgreSQL Company
>  

> On Apr 2, 2019, at 2:16 AM, Dave Page <dpage@pgadmin.org> wrote:
>
> The only change I'm inclined to make here is to change the Save button on the popup to say "OK" or similar to remove
theimplication that the data will actually be saved rather than just updated in the grid. 

That’s an excellent idea.

--
John Abraham

Sent from my iPhone, please excuse any typos.