| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)yahoo(dot)com> |
| Cc: | ldrlj1 <russelljanusz(at)masterpeaceltd(dot)com>, pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: PGAdmin Version 2.1 |
| Date: | 2018-01-30 15:01:47 |
| Message-ID: | CA+OCxoxS8_rFokUTpiGtuk+TMO2eC=tcKfc=dmShTY0JGxN_yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Tue, Jan 30, 2018 at 2:57 PM, Melvin Davidson <melvin6925(at)yahoo(dot)com>
wrote:
>
> *>Effectively, a composite type that can represent a row in a class*
>
> *That may be true, but users expect to see "user defined types", not
> tables and views. As such, the query driving the display should be
> something like:*
>
>
>
>
>
>
>
>
>
>
>
>
> *WITH types AS( SELECT reltype FROM pg_classWHERE relkind = 'c')SELECT
> * FROM pg_type WHERE oid in (SELECT reltype FROM
> types) ORDER BY typname;No need to duplicate everything else.*
>
No - if you switch on "Show system objects", it will display system objects
such as row types. That's the whole point of the switch (which is off by
default).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2018-01-30 15:22:22 | Re: PGAdmin Version 2.1 |
| Previous Message | Melvin Davidson | 2018-01-30 14:57:25 | Re: PGAdmin Version 2.1 |