...

Thu, 21 Feb 2013 02:38:27 -0800 (PST)21 Feb 2013 02:38:27 -0800 (PST)
X-Newsgroups: pgsql.interfaces.pgadmin.support
Date: Thu, 21 Feb 2013 02:38:26 -0800 (PST)
In-Reply-To: <50F81D1A.4000009@ifortuna.cz>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=79.121.57.95;
posting-account=Qgz6DQoAAABy7twg8l6on0iP0KA6BAvN
References: <201301171356.r0HDu4is091671@news.hub.org>
<BLU0-SMTP108045710865BD17B078BA0CF130@phx.gbl><50F81D1A.4000009@ifortuna.cz>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e9ef9bd0-5454-41e7-8e80-db88e2043777@googlegroups.com>
Subject: Re: Editable resultset
From: durumdara@gmail.com
Injection-Date: Thu, 21 Feb 2013 10:38:27 +0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
To: pgadmin-support@postgresql.org

2013. janu=C3=A1r 17., cs=C3=BCt=C3=B6rt=C3=B6k 16:47:38 UTC+1 id=C5=91pont=
ban Michal Kozusznik a k=C3=B6vetkez=C5=91t =C3=ADrta:
> I think the feature you are looking for is obtained using right click=20
>=20
> over table and selecting "View data... filtered rows".
>=20
> > It's live and editable.
>=20
> >
>=20
> >
>=20
>=20
>=20
> Yes it is. But is not comfy enough for daily work
>=20
> It is implemented very well in MySQL software (Query Browser and=20
>=20
> Workbench). You can edit resultset retrieved  by SELECT statement since=
=20
>=20
> it's identified by PK or Unique key, right after executing this statement=
.
>=20
> The method provided by pgadmin is not always efficient. There are a few=
=20
>=20
> reasons:
>=20
> - you cannot define columns set displayed in the grid - with a lot=20
>=20
> columns in a table, while not all fit the window, working with it is=20
>=20
> annoying
>=20
> - you cannot change order of displayed columns - as above
>=20
> - using filter and sort tabs is significantly slower then writing SELECT=
=20
>=20
> in query window
>=20
> - usually (from experience) you start to work with query window. Then=20
>=20
> after got result, you have to execute select via View Data just to be=20
>=20
> able to edit it. Sometimes writing update query is faster (again, from=20
>=20
> experience)
>=20
>=20
>=20
> So, I also vote to make resultsets retrieved by select statement editable=
.
>=20
>=20
>=20
> with regards
>=20

Hi!

I totally agreed with Michal.
See HeidiSQL, EMS Managers, and so on.
DBeaver is also seems to be good - but Java driver don't supports the live =
result (Otherwise we would edit the Query rows).

The table filters (as I see) don't support the subqueries.
So if I want filter with:
select * from a
where a.id in (select ....)
I can't do it...

This is tricky thing.
When I use Delphi and Zeos package, I easily can use live queries - if the =
SQL supports them.

But I don't want to develop a new manager program...=20
So it is strange (for me) that how the MySQL interfaces have great guis wit=
h many functions, and how the "poor" PGSQL miss same quality of gui (in fre=
e products).=20

Why the people were upgraded these tools only in MySQL world, and not in PG=
SQL...? :-( It is a sad story for me that when I want to use Free Tools, th=
en I everytime blocked by some little things in PGSQL side which is realize=
d in MySQL side. I'm not happy to see this, but I wondering: how the MySQL =
have background to write overdeveloped free products (like HeidiSQL), and w=
hy these products are non-free in PGSQL side?


Best Wishes: dd