Thread: Request: get rid of annoyance with new SQL window
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.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
On Fri, Mar 19, 2010 at 6:45 PM, Josh Berkus <josh@agliodbs.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
> That behaviour hasn't changed in years. It sounds like you turned on
> the 'Copy SQL from main for to query tool' option.
I didn't do it manually; somehow it got set to that when I upgraded.
Thanks for the option, turned off now.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
On Fri, Mar 19, 2010 at 6:56 PM, Josh Berkus <josh@agliodbs.com> wrote: > >> That behaviour hasn't changed in years. It sounds like you turned on >> the 'Copy SQL from main for to query tool' option. > > I didn't do it manually; somehow it got set to that when I upgraded. > Thanks for the option, turned off now. More likely when you deleted the preferences file when trying to figure out the display issue you reported I'd wager. There's no reason I can see why an upgrade would (or even could) toggle and existing setting. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do
> More likely when you deleted the preferences file when trying to
> figure out the display issue you reported I'd wager. There's no reason
> I can see why an upgrade would (or even could) toggle and existing
> setting.
Oh, yeah, that's most certainly possible. Since I deleted that file
several times.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com