Just an observation..... :)
With the 1.14 stream of pgadmin3, I notice that the dialog for creation of columns moves the type to a different tab than the name, requiring much more work to create the columns.
Is there a reason why this was done? The old way seemed to work nicer for me - ie: most of the needed bits were all on one tab to quickly add a column, go to other tabs only if needed.
From: pgadmin-support-owner(at)postgresql(dot)org [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Dave Page
Sent: Wednesday, May 11, 2011 7:27 AM
To: Bob McConnell
Cc: gabriele(dot)garuglieri(at)infoblu(dot)it; bneuhauser(at)real(dot)com; guillaume(at)lelarge(dot)info; pgadmin-support(at)postgresql(dot)org
Subject: Re: [pgadmin-support] Usability improvment ideas
On Wed, May 11, 2011 at 1:18 PM, Bob McConnell <rvm(at)cbord(dot)com> wrote:
> From: gabriele.garuglieri
>> Dave Page <dpage(at)pgadmin(dot)org> scritti il 11/05/2011 10:12:33
>>> We could pretty easily add options
>>> for "execute current line" and "execute current paragraph" (I'd find
>>> those very useful in fact).
>> Those would be greatly welcome!!
> If I might add a suggestion. I have occasion to use Sybase ASA and the
> Interactive SQL tool that comes with it. In that application, when I hit
> F9 it will execute all of the SQL statements in that window. But if I
> highlight one or more of several statements, as if I were copying them,
> then hit F9, it will only execute the highlighted statements.
pgAdmin already does that (though, with F5, not F9).
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
In response to
pgadmin-support by date
|Next:||From: hatem gamal elzanaty||Date: 2011-05-12 20:58:21|
|Subject: facing problem in accessing postgresql with c language normally|
|Previous:||From: Peter Geoghegan||Date: 2011-05-12 15:42:27|
|Subject: Re: SQL Editor fail|