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
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
O Achilleus Mantzios έγραψε στις Sep 20, 2005 :
>
> 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 nee
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
