Idea: check SQL before copying to SQL dialogue. - Mailing list pgadmin-hackers

From Erwin Brandstetter
Subject Idea: check SQL before copying to SQL dialogue.
Date
Msg-id 4E270AF7.2030209@falter.at
Whole thread Raw
Responses Re: Idea: check SQL before copying to SQL dialogue.  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Aloha!

A lot of work has been put into when and where to refresh the browser window.

 From my experience it is often a _good_ thing, that changes via SQL are not reflected in the browser window
immediately.Serves me well as a poor  
man's undo-tool.
On the other hand, one tends to forget about refreshing the browser, especially casual users who are not aware on what
occasionsthe browser's display  
is refreshed automatically.
The major pitfall is with the option "Copy SQL from main form to SQL dialogue" - and most people use that one. If you
forgetto refresh beforehand,  
you may lose your most recent changes and may not even notice it.
Keeps happening to me.

How about this idea?
- Whenever the "Copy SQL from main form to SQL dialogue" feature kicks in, check if the displayed SQL is the latest
version.
- If not, ask the user whether he wants the latest instead. (DO ask!)
(We already have a similar check befor saving anything from a properties dialog.)

Anybody trying hard enough can still screw up, with copy / paste, for instance. But this idea would take care of the
majorpitfall for me. 

Any +1's on this?


Regards
Erwin



pgadmin-hackers by date:

Previous
From: "pgAdmin Trac"
Date:
Subject: Re: [pgAdmin III] #164: Missing login roles in properties dialog
Next
From: "pgAdmin Trac"
Date:
Subject: Re: [pgAdmin III] #164: Missing login roles in properties dialog