From: | GPT <gptmailinglists(at)gmail(dot)com> |
---|---|
To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Adding an extra boolean column to "information_schema.columns" or "pg_attribute" |
Date: | 2017-12-30 19:33:28 |
Message-ID: | CADep2PPgC33fxDLPmH+U91bvzBECtFyu_RzCA4ZBo6MXTL+41A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Please visit the following link:
https://stackoverflow.com/q/48028501/8895614
but thing may go further/deeper than it seems.
Krds
On 12/30/17, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> wrote:
> On Sat, Dec 30, 2017 at 08:17:34PM +0100, GPT wrote:
>
>> I would like to add an extra boolean attribute to table columns,
>> something like NULL. Unfortunately Pg does not support such a feature:
>>
>> ADD ATTRIBUTE <attribute_name> TYPE <type_of_attribute> TO COLUMN
>> <schema.table.column_name>;
> ...
>> I have already been suggested to use VIEW or dynamic SQL but I am
>> looking something different.
>
> Can you explain why ?
>
> One thing that comes to mind is complex user types.
>
> Or columns of type table.
>
> Karsten
> --
> GPG key ID E4071346 @ eu.pool.sks-keyservers.net
> E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | PT | 2017-12-30 20:08:32 | Re: Adding an extra boolean column to "information_schema.columns" or "pg_attribute" |
Previous Message | Karsten Hilbert | 2017-12-30 19:23:10 | Re: Adding an extra boolean column to "information_schema.columns" or "pg_attribute" |