On Sun, 27 Aug 2000, Miles Thompson wrote:
> Other columns could simply be labelled "descrip1", "descrip2", "descrip3", as
> many as you need, for the different attributes of each item. So "descrip1" may
Now someone once said to me "If you find your labeling your fields x1, x2,
x3... then your design is wrong." His next step would be to ask for your
ER diagram :-)
Have you tried inheritance? i.e you will have a product, inheriting from
that you will have computers, boats, cars etc. Perhaps from boats you
could have sail boats, motor boats etc as you store different attributes.
As postgresql is an OORBMS it should be able to handle it without any
nasty squash into the relational model tricks.
I've never used an OO database in production mind you...perhaps there is
some catch I'm not aware of.
Andrew
