Kynn Jones wrote:
I have two classes of objects, A and B, where B is just a special case
of A. (I.e., to describe a B-type object I need to specify the same
fields as for an A-type object, plus a whole bunch additional fields
specific to B alone.) Furthermore, there's a third class T that is in
a many-to-one relation with A (and hence also B) objects.
The question is, what's the "best practice" for implementing this
situation in PostgreSQL. My first idea was to define B as inheriting
from A, which is OK, except that I have not figured out how to
implement the reference from T. Is inheritance indeed the right tool
for this problem, or should I use a different approach?
It seems that inheritance is precisely what you want.
WRT yout table T you should be able to join to B in the same way you
would join to A. But perhaps you should give an example of both B & T
(and maybe A).
brian
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
