Hi,

I am thinking of using the inheritance feature of PQ but have some
problems with it.
As far as I read the documentation foreign-key support, row-locking,
indexing etc. is very limited or not completly available with
inheritance.
From this information I get the feeling that inheritance is not realy
maintained or depreceated in some way.
Should I go for a real relational model instead?

thanks for any answers

Sascha

Sascha Bohnenkamp <asbohnenkamp (AT) gmx (DOT) de> wrote:
I guess it depends what you want.

Inheritance is probably good for some things, like when you want
to make sure that the definition of "inherited" columns stays the same
between parent and child, or you want to make use of the feature that
querying the parent will return child rows.
For example, if you want to implement partitioning.

If you don't need these features, it's probably best to not use it,
because it does not always "work the way you expect"; basically parent
and child are independent objects for most purposes.

I don't believe that the feature is deprecated or likely to vanish,
I'd rather say that it dows not 100% integrate with other PostgreSQL
behaviour.

Yours,
Laurenz Albe

thank you that realy did help to decide

I was just wondering about it because it seems to be unchanged for
more than ten years if I saw it right .. telling me that it may
integrate better in some future version.