public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Chris Travers <[email protected]>
Cc: Postgres Documentation <[email protected]>
Subject: Re: Thoughts on inheritance docs
Date: Thu, 23 Aug 2012 10:09:57 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKt_ZfumToYZEy1U+a9+xkRmOt2nCmWR=eFgJrep6tJZkdLRMg@mail.gmail.com>
References: <CAKt_ZfumToYZEy1U+a9+xkRmOt2nCmWR=eFgJrep6tJZkdLRMg@mail.gmail.com>
Chris Travers <[email protected]> writes:
> 1) Would it be worth coming up with more useful examples for table inheritance?
> 2) Would it be worth adding mention of uses of multiple table inheritance?
> 3) Would it be worth discussing how to position the limitations of
> table inheritance? I personally recognize the difficulties in
> documenting these but I can't help thinking that a simple chart of
> "this is/is not inherited" would be very useful as well.
All of those sound sane to me at this level of detail, and in particular
I agree that the docs are short on examples of multiple inheritance.
The arguments will probably start once you get more concrete ...
regards, tom lane
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Thoughts on inheritance docs
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox