Re: Better support for whole-row operations and composite types - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Better support for whole-row operations and composite types
Date
Msg-id 14491.1080602138@sss.pgh.pa.us
Whole thread Raw
In response to Re: Better support for whole-row operations and composite types  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Greg Stark <gsstark@mit.edu> writes:
> If I understand what you're talking about, you would be allowed to
> CREATE TYPE a composite type, like say, "address" and then use that as
> a datatype all over your database? And then if you find "address"
> needs a new field you can add it to the type and automatically have it
> added all over your database to any table column using that type?

I believe that would work, though you might have some issues with cached
plans.

> How will client programs see the data if i do a "select *"?

TBD.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Manfred Koizar
Date:
Subject: Re: PostgreSQL block size vs. LVM2 stripe width
Next
From: "Dann Corbit"
Date:
Subject: Win32 compatibility now broken for Microsoft and Intel Windows compilers even for Libpq in current snapshot