Re: Schema design: user account deletion vs. keeping family tree data
| От | Rob Sargent |
|---|---|
| Тема | Re: Schema design: user account deletion vs. keeping family tree data |
| Дата | |
| Msg-id | A7C6E015-5E15-45BC-8AEB-9A55FD9B2DF5@gmail.com обсуждение исходный текст |
| Ответ на | Re: Schema design: user account deletion vs. keeping family tree data (Christoph Pieper <christoph@fecra.de>) |
| Список | pgsql-general |
> On Nov 26, 2025, at 3:25 PM, Christoph Pieper <christoph@fecra.de> wrote: > > Thanks everybody! > > And what do you think about Option A? > Especially the pedigree node approach beside the animal node? I have to ask if you are thinking about genetics or genealogy. Your opening statement certainly implies the former. Thatyou will have many many users tends towards the latter. With respect to genetics I repeat myself (and another responder): keep the triplet table simple as can be with ego-mother-father.All else is fluff. ;) You will have to lose/break pedigrees in the event of a deletion/retraction. Keepin mind that there is a school of thought that claims pedigrees are in fact identifying information. For genealogy you might work off a two table setup: person and relationship. The former defines an id and the latter relatestwo persons with a specific type of relationship including half sibs, step sibs, uncle/aunt - whatever your userswish to tell you
В списке pgsql-general по дате отправления: