Re: SQL worksheet

Поиск
Список
Период
Сортировка
Искать

Re: SQL worksheet

От:
"Dave Page" <dpage@vale-housing.co.uk>
Дата:
 

> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e@gmx.net] 
> Sent: 23 April 2004 15:11
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] SQL worksheet
> 
> I open the SQL worksheet (icon "pen with SQL"), immediately 
> select File -> Quit, then it informs me that there are 
> changes and if I want to save them.  
> But I didn't change anything.  Is it possible to fix that?

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?

Regards, Dave.

Re: SQL worksheet

От:
"Dave Page" <dpage@vale-housing.co.uk>
Дата:
 

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] 
> Sent: 27 April 2004 12:23
> To: Dave Page
> Cc: Peter Eisentraut; pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] SQL worksheet
> 
> Let's fix it. I didn't notice, because I use the "never ask" option.

OK, fixing...

SQL worksheet

От:
Peter Eisentraut <peter_e@gmx.net>
Дата:
I open the SQL worksheet (icon "pen with SQL"), immediately select File -> 
Quit, then it informs me that there are changes and if I want to save them.  
But I didn't change anything.  Is it possible to fix that?

Re: SQL worksheet

От:
Andreas Pflug <pgadmin@pse-consulting.de>
Дата:
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
FAQ