Re: [GENERAL] What's the benefit (or usage scenario) of a "typedtable"? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: [GENERAL] What's the benefit (or usage scenario) of a "typedtable"?
Date
Msg-id e3d9bff5-efc5-019e-0831-42795d8a20bb@aklaver.com
Whole thread Raw
In response to Re: [GENERAL] What's the benefit (or usage scenario) of a "typed table"?  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-general
On 12/31/2016 08:25 AM, Thomas Kellerer wrote:
> David G. Johnston schrieb am 31.12.2016 um 16:51:
>>>  I wonder what the benefit of a typed table is and when this would be
>>> useful?
>>
>> But I'd say if you want a table with said structure you should plan on
>> droppign the original type after you've altered all references to it to
>> point to the new implicit type created with the table.
>
> I am not planning to use it.
>
> I am just wondering _if_ there is an advantage to this setup
>
> Apparently at some point someone thought it would be useful, otherwise
> it wouldn't have been implemented I guess.

I see it as completing the loop. A table creates a composite type, a
composite type creates a table. Not sure where that falls on the useful
scale.

>
> Thomas
>
>
>
>
>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] What's the benefit (or usage scenario) of a "typed table"?
Next
From: Chris Withers
Date:
Subject: Re: [GENERAL] default representation of null in psql