>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).
Except that "system objects" are NOT USER tables, views, indexes, etc.
They are _system_ catalogs and views;
Your definition is a behavior change from PgAdmin III, which DID NOT show every
"system object" per your definition". It only showed USER types as permy query.
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 Tuesday, January 30, 2018, 10:01:50 AM EST, Dave Page
<[email protected]> wrote:
On Tue, Jan 30, 2018 at 2:57 PM, Melvin Davidson <[email protected]> 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_class
WHERE 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
