Re: Some thoughts on table inheritance (which is uniquely awesome on PostgreSQL)

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Some thoughts on table inheritance (which is uniquely awesome on PostgreSQL)
Date: 2012-08-24 02:04:01
Message-ID: CAKt_ZfvB4q25+e0ZQGSF4CWBDd0z7Whyb=ofXy_VuoU41FTDEQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

One other thing that seems worth mentioning is that as soon as you
jump from relational to object-relational modelling is that the latter
is more rich and hence more complex than the former. Because
object-relational modelling is a much expanded semantic superset of
relational modelling, the antipatterns are a much expanded superset
there too. Additionally because the patterns are not yet well
understood, the whole area needs to be seen as somewhat immature.

That doesn't mean that the features are primarily useful as foot-guns,
but it does mean that productive use of features like this involves
careful documentation of patterns and antipatterns.

Best Wishes,
Chris Travers

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2012-08-24 02:12:20 Re: Can column name aliases be supported?
Previous Message Jeff Davis 2012-08-24 02:00:02 Re: FETCH in subqueries or CTEs