Melvin Davidson 🎸
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com
On Monday, November 6, 2017, 10:23:04 AM EST, Cherio <[email protected]>
wrote:
Thank you for elaborating!! pgadmin 4 is a great product.
I still hope that in some future at least the explorer view can get the
"Aggregates" node, at least as an informational one. From my experience most of
the time creating DB objects (tables, functions, etc) is done via a script so
the UI to create DB objects is rarely used. However when it comes to exploring
DB structure a lazy sloth like DB developer likes the explorer tree :) It is
far more convenient to navigate the tree than to type queries.
On Mon, Nov 6, 2017 at 12:13 AM, Ashesh Vashi <[email protected]>
wrote:
On Mon, Nov 6, 2017 at 10:34 AM, Khushboo Vashi <[email protected]
om> wrote:
On Sat, Nov 4, 2017 at 1:10 AM, Cherio <[email protected]> wrote:
After switching from desktop version 3 to the latest 4 2.0 I noticed that
"Aggregates" node is missing from schemas. It is also missing in
"Preferences"->"Browser"->"Nod es". I am not sure if this is a bug or an issue
with my local environment or it has not been implemented.
pgAdmin 4 does not support "Aggregates".
While porting some of the PostgreSQL object nodes from pgAdmin 3 to pgAdmin 4,
we found good number of bugs (which were there from long time) in pgAdmin 3.
And, nobody reported it back to communitiy. That indicates - they were not
being used by any user.So - it was conscious decision to remove those nodes
from pgAdmin 4.
--Thanks & Regards,
Ashesh Vashi
Thanks!
A simple query of SELECT * FROM pg_aggregateORDER BY aggtransfn;
ought to suffice. Add specific column names and WHERE clause to tailor to your
needs.
