From: | Killian Driscoll <killian(dot)driscoll(at)ucd(dot)ie> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Create view that retrieves both table and column comments |
Date: | 2016-02-18 21:31:44 |
Message-ID: | CAFTc7AdSdWssH8_rbmr=ypZXmKRv31RD9Up-fnENpHk6Aes-pA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 18 February 2016 at 22:22, Joe Conway <mail(at)joeconway(dot)com> wrote:
> On 02/18/2016 01:15 PM, Killian Driscoll wrote:
> > On 18 February 2016 at 22:01, Joe Conway wrote:
> > WHERE NOT n.nspname LIKE 'pg\_%'
> > AND NOT n.nspname = 'information_schema'
> > AND a.attnum > 0
> > AND c.relkind = 'r'
> > UNION ALL
>
> > This works - thank you. I see in column "a.attname as column_name",
> > there are a few rows with data like '......pg.dropped.3.....': what are
> > these?
>
> Those are columns that have been dropped after the table was created.
> You could filter those out by adding
>
> AND NOT a.attisdropped
>
> into the WHERE clause before the UNION ALL
>
> Joe
>
> --
> Crunchy Data - http://crunchydata.com
> PostgreSQL Support for Secure Enterprises
> Consulting, Training, & Open Source Development
>
>
--
Killian DriscoIl
IRC Postdoctoral Fellow
UCD School of Archaeology
University College Dublin
academia.edu/KillianDriscoll <https://ucd.academia.edu/KillianDriscoll>
www.lithicsireland.ie
ca.linkedin.com/in/killiandriscoll
From | Date | Subject | |
---|---|---|---|
Next Message | Killian Driscoll | 2016-02-18 21:32:37 | Re: Create view that retrieves both table and column comments |
Previous Message | Joe Conway | 2016-02-18 21:22:11 | Re: Create view that retrieves both table and column comments |