pgAdmin developer tools

2018-03-14 Thread peter verbeek
Hello,

It is about DELETE row in the UI

When I execute a query via the context menu browser tree View/Edit Data and 
select a row the DELETE button becomes active and I am able to delete a row.
There is only a limited possibility to modify this query with the filter and 
the number of rows pulldown.

When I execute a query with the Query Tool I am NOT able to delete a row. The 
delete button is NOT active.

I would like to make my own query and delete some rows from the result.
Did not find a way to do this.

Is this “works as designed” or am I missing something?

BTW: In the documentation “Reviewing and Editing data” the description of the 
DELETE button is wrong.

Thanks,

peter


Re: Faded text in pgAdmin 4 2.0/Win Server 2008r2

2018-03-14 Thread noAnymous
Hi Dave,


Dave Page-7 wrote
> Please try the test build at
> https://developer.pgadmin.org/~dpage/pivotal/pgadmin4-3.0-dev-x86.exe

did so and the fonts look fine and are readable without eye cancer. ;-)

But:
 - the GUI was not rendered in a separate OS-window (like when the problem
was observed) but within a new browser tab
 - on the first run, all the previuosly configured servers were absent, the
servers node in the tree was empty
- on the second run all the servers were shown and were accessible as
expected






--
Sent from: 
http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html



Re: Faded text in pgAdmin 4 2.0/Win Server 2008r2

2018-03-14 Thread Dave Page
On Wed, Mar 14, 2018 at 11:12 AM, noAnymous <
vhwftl1rzizurxvgg...@discardmail.com> wrote:

> Hi Dave,
>
>
> Dave Page-7 wrote
> > Please try the test build at
> > https://developer.pgadmin.org/~dpage/pivotal/pgadmin4-3.0-dev-x86.exe
>
> did so and the fonts look fine and are readable without eye cancer. ;-)
>
> But:
>  - the GUI was not rendered in a separate OS-window (like when the problem
> was observed) but within a new browser tab
>

Yes, that's intentional.


>  - on the first run, all the previuosly configured servers were absent, the
> servers node in the tree was empty
> - on the second run all the servers were shown and were accessible as
> expected


That's weird though. Can you reproduce it still?

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company