From: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-sql@postgresql.org
Subject: Re: Inheritance (general hints wanted)
Date: Wed, 21 Sep 2005 09:23:13 +0300 (EEST)
Message-ID: <Pine.LNX.4.44.0509210909570.18668-100000@matrix.gatewaynet.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0509201350240.16480-100000@matrix.gatewaynet.com>
Judging from the replies i got, it seems that
inheritance is even less used than i initially thought.
I think that the OO term is a little too much advertised
in pgsql advocacy various acts, than actually engineered.
However, OO in pgsql besides being a traditionally cool
acronym, it also *could* prove to be extremely useful
when dealing with real problems.
Just a question, to all those who have implemented
inheritance in pgsql:
Are there any plans for dealing with the current problems?
Is it foundamentally hard to fix these problems?
--
-Achilleus
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: pgsql-sql@postgresql.org
Cc: achill@matrix.gatewaynet.com
Subject: Re: Inheritance (general hints wanted)
In-Reply-To: <Pine.LNX.4.44.0509210909570.18668-100000@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox