X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 76464D86E5 for ; Tue, 20 Sep 2005 04:02:33 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60927-03 for ; Tue, 20 Sep 2005 07:02:29 +0000 (GMT) Received: from matrix.gatewaynet.com (matrix.gatewaynet.com [217.19.69.50]) by svr1.postgresql.org (Postfix) with ESMTP id A50C6D84A6 for ; Tue, 20 Sep 2005 04:02:27 -0300 (ADT) Received: from matrix.gatewaynet.com (localhost.localdomain [127.0.0.1]) by matrix.gatewaynet.com (8.12.8/8.12.8) with ESMTP id j8K6tH2n016064 for ; Tue, 20 Sep 2005 09:55:17 +0300 Received: from localhost (achill@localhost) by matrix.gatewaynet.com (8.12.8/8.12.8/Submit) with ESMTP id j8K6tHeQ016060 for ; Tue, 20 Sep 2005 09:55:17 +0300 Date: Tue, 20 Sep 2005 09:55:17 +0300 (EEST) From: Achilleus Mantzios To: pgsql-sql@postgresql.org Subject: Inheritance (general hints wanted) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.009 required=5 tests=[AWL=0.009] X-Spam-Level: X-Archive-Number: 200509/174 X-Sequence-Number: 22721 Hi, I think i have reached a point in my PgSQL years that i am seriously thinking of using inheritance. The situation is simple: An new entity (tanker vessels crew) is about to be modeled, and i suspect there will be a future need to include the rest of 'workers' besides 'sailors', IOW i suspect a future need to generalize. So i am thinking of a two-level tree hierarchy, where there is a simple table emp (employee), and a direct child 'tankerscrew'. Later there may be 'masons', 'office_employees' and so on. The problem is that while i find this approach attractive, i have never used PostgreSQL inheritance exhaustively and in production scale. Furthermore, i also feel that not many people have used inheritance in a massive fashion (besides playing with a test db). Of course i can do it with separate uncoupled tables, that can be later related with some views. So that leads to the final question: -What are the main PROs of inheritance that cant be beat by other solutions, and -Are there any traps someone must have in mind when he prepares for such a design? Thanx in advance. -- -Achilleus