Issues with v1.10 beta 1

From: Kieran McCusker <kieran(dot)mccusker(at)kwest(dot)info>
To: pgadmin-support(at)postgresql(dot)org
Subject: Issues with v1.10 beta 1
Date: 2009-03-25 13:19:20
Message-ID: 49CA2F58.10402@kwest.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi

I have been using beta 1 for a few days now. It's looking good but could
I mention the following items:

*Query tool Ctrl-E*
Selecting the Query tool opens with the contents of the SQL pane which
it didn't in 1.8.4. I think this behaviour is fine except when you go to
open the query file you actually want to work on. You now get the dialog
"the text has changed. Do you want to save changes?" which of course it
hasn't.

Block indenting logic has changed
I have tabs set to spaces and indent set to 2. If I have a block where
the first line(s) are indented by one more space than the final line it
is not possible to get the block to align using keyboard. Also in 1.8.4
the line the cursor was on was excluded from block indent whereas it is
now included which makes it a bit more awkward to use.

*Execute pgScript.*
Took me little while to figure out how to use this - probably me being
dumb! When I first added the pgScript and pressed F5 it took me a while
to understand why it didn't work. When I figured out it was F6 all was
well except that my final query results didn't appear in the output pane.
Would it be possible for the results of the last query to be sent to the
output pane?
I also wondered about F5 giving a clearer message if pgScript was detected?

Many thanks for a great product.

Kieran

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Weitzel 2009-03-25 13:27:02 pg_dump version mismatch
Previous Message fabian lopez 2009-03-25 13:09:17 Soporte tecnico sobre la Base de Datos de PostgreSQL