pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: thomas.silvi <thomas.silvi@laposte.net>
To: achill <achill@matrix.gatewaynet.com>
Cc: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: Inheritance (general hints wanted)
Date: Tue, 20 Sep 2005 12:07:32 +0200
Message-ID: <IN41GK$D844731D6E7692029C2CA7216473BDB8@laposte.net> (raw)


       Hi,
  I am not an expert but in object conception, a design pattern
  exists for the case you describe.  I don't remember which
one. The idea is to add an attribute that references the job
of the employee. The inheritance is not on the side of the
employee but on the side of the job. So if the job of the
employee changes, it easy to do it.

an example in pseudo-code

class basic_job
     string      name

class sailor_job inherit basic_job

class employee
     string      name
     basic_job   job          
    

  Hope it helps,

      Regards,
          Thomas
> 
> 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
> 
> 
> ---------------------------(end of
broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
> 

 A+
    Tom

Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,34€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)






view thread (4+ messages)  latest in thread

Message-ID: <IN41GK$D844731D6E7692029C2CA7216473BDB8@laposte.net>
Permalink:  ../IN41GK$D844731D6E7692029C2CA7216473BDB8@laposte.net/
Also on:    postgresql.org/message-id/IN41GK$D844731D6E7692029C2CA7216473BDB8@laposte.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: thomas.silvi@laposte.net, achill@matrix.gatewaynet.com
  Subject: Re: Inheritance (general hints wanted)
  In-Reply-To: <IN41GK$D844731D6E7692029C2CA7216473BDB8@laposte.net>
  References: <IN41GK$D844731D6E7692029C2CA7216473BDB8@laposte.net>

* 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