| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Request: get rid of annoyance with new SQL window |
| Date: | 2010-03-19 18:49:03 |
| Message-ID: | 937d27e11003191149j7caa39b2n131046cea83cb90a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Fri, Mar 19, 2010 at 6:45 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> New annoyance for 1.10.1:
>
> 1) connect to a server
> 2) click on a database
> 3) click the "SQL" button to open a new SQL window
> 4) the text of the database definition will be in that SQL window
> 5) use file ... open to open the file you actually wanted to edit
> 6) get prompt "The text has changed. Do you want to save the changes?"
>
> This is annoying and unnecessary; when I click the SQL button, I should
> get a *blank* query window, as I used to in 1.10.0. I should only get
> the object definition if I select "Scripts" from the context menu.
That behaviour hasn't changed in years. It sounds like you turned on
the 'Copy SQL from main for to query tool' option.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-03-19 18:56:43 | Re: Request: get rid of annoyance with new SQL window |
| Previous Message | Josh Berkus | 2010-03-19 18:45:08 | Request: get rid of annoyance with new SQL window |