Browsing the docs last night, I realized that I've never taken
advantage of Postgres' powerful composite types. But a question came
to mind- in what scenarios should you use a composite type in a table
structure? That is, I can see the benefits of a composiite type
insofar as it essentially lets you add virtual tuples to a table
without having to alter the table structure to add new fields.
Instead you can simply extend the composite type. But why take this
approach?
http://www.postgresql.org/docs/8.4/static/rowtypes.html
