I do not have any intention to persuade anyone. The time runs faster
than any committee!
My question was very clear because I do not know the Pg's internal and
I would like to zero the side (fatal) (if any) effect.
So please, if you really know, tell me if there will be any problem in
case I defi
ally in IT "art" sector.
So, adding an extra boolean column to "information_schema.columns" or
"pg_attribute" will cause any "fatal" problem in the present?
Krgds
On 12/30/17, PT wrote:
> On Sat, 30 Dec 2017 20:33:28 +0100
> GPT wrote:
>
>> Pleas
GPT writes:
> I would like to add an extra boolean attribute to table columns,
The contents of the information_schema views are specified by the SQL
standard (ISO 9075). Since the entire point of having those views is to
have a standard-conformant way of accessing the information in the system
c
On Sat, 30 Dec 2017 20:33:28 +0100
GPT wrote:
> Please visit the following link:
>
> https://stackoverflow.com/q/48028501/8895614
>
> but thing may go further/deeper than it seems.
Adding columns to a built-in system table is liable to cause all sorts of
problems in the future: when you upgrad
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 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,
>>
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 TYPE TO COLUMN
> ;
...
> I have already been suggested to use VIEW or dynamic SQL bu
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 TYPE TO COLUMN
;
For example:
ADD ATTRIBUTE is_displayed TYPE boolean TO COLUMN world.human.feature;
so that I can write:
SELECT column_name F
