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

From David G. Johnston
Subject Re: [GENERAL] What's the benefit (or usage scenario) of a "typed table"?
Date
Msg-id CAKFQuwb8K4ZRwO_ooY2b4U8yAQmfcLX3TEeNfoMKRJqEHYdvow@mail.gmail.com
Whole thread Raw
In response to [GENERAL] What's the benefit (or usage scenario) of a "typed table"?  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: [GENERAL] What's the benefit (or usage scenario) of a "typed table"?
List pgsql-general
On Saturday, December 31, 2016, Thomas Kellerer <spam_eater@gmx.net> wrote:
I recently stumbled over "typed tables" in Postgres
(there were several questions containing this on stackoverflow recently)

    create type some_type as (id integer, data text);
    create table some_table of some_type;

I wonder what the benefit of a typed table is and when this would be useful?

Given that I'd frown upon having two types with identical structure I'd say this is could be harmfull if swallowed.  Thoguh it might find use in refactoring and maintaining backward compatibility.  It does setup an object dependency which is the only visible difference from just copy the type definition into the CREATE TABLE.  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.

David J.

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: [GENERAL] What's the benefit (or usage scenario) of a "typed table"?
Next
From: Thomas Kellerer
Date:
Subject: Re: [GENERAL] What's the benefit (or usage scenario) of a "typed table"?