Advice about a parent-child relation design

From: JORGE MALDONADO <jorgemal1960(at)gmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Advice about a parent-child relation design
Date: 2015-11-21 17:45:12
Message-ID: CAAY=A7-CjNzc-rev0rNuq86_=AS3sPqJPsE3jQk2WLcRe_tbvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

I have 2 tables: parent and child. One of the fields, which should
supposedly be part of the parent table, might occassionaly be different for
one of the child table records.

ParentTable
* id
* date
* customer <-----
* reference
* other fields...

ChildTable
* id-parent
* document type
* customer <-----

It is possible that the customer field is not the same for all of the child
records. This is a very specific (and strange) situation that might
eventually appear in the information system I am developing. I suppose that
such a field must be part of the child table even if this case does not
appear frequently.

I am writing to ask for your feedback and see if there is another possible
approach.

With respect,
Jorge Maldonado

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Felipe Santos 2015-11-21 19:53:58 Re: Advice about a parent-child relation design
Previous Message =?UTF-8?Q?=E9=A9=AC=E4=BF=AE/=D0=9C=D0=B0=D1=82=D0=B2=D0=B5=D0=B9/Mateo/M?==?UTF-8?Q?att=20Buse?= 2015-11-21 02:00:10 Re: Combine Top-k with similarity search extensions