From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgadmin-support(at)postgresql(dot)org |
Subject: | Re: SQL worksheet |
Date: | 2004-04-27 11:23:17 |
Message-ID: | 408E42A5.5060101@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Dave Page wrote:
>
>
>This is the intended behaviour, though I grant you this one is
>definitely open to debate. The behaviour you describe occurs when
>'StickySQL' is switched on, such that the current statement in the main
>form is automatically loaded into the SQL textbox - th theory being that
>the copied SQL constitutes a change. When 'StickySQL' is turned off,
>this does not occur. Looking at the code this is definitely by design
>and not by accident.
>
>The question is, is this correct behaviour? I'm erring on Peter's side
>as it seems that the no change option would comply with the principle of
>least astonishment...
>
>Any other opinions?
>
Let's fix it. I didn't notice, because I use the "never ask" option.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-04-27 11:27:25 | Re: [pgADMIN] Windows - can't type some polish |
Previous Message | Tomasz Kubacki | 2004-04-27 08:42:17 | Re: [pgADMIN] Windows - can't type some polish |