Re: Schema design: user account deletion vs. keeping family tree data

public inbox for [email protected]  
help / color / mirror / Atom feed

From: Rob Sargent <[email protected]>
To: Christoph Pieper <[email protected]>
Cc: [email protected]
Subject: Re: Schema design: user account deletion vs. keeping family tree data
Date: Wed, 26 Nov 2025 16:26:48 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEzggP9TjxdAGNHzjJJGcuGstT-9NzBm24SJc9UcmRQYnZVFDQ@mail.gmail.com>
References: <CAEzggP9TjxdAGNHzjJJGcuGstT-9NzBm24SJc9UcmRQYnZVFDQ@mail.gmail.com>

> On Nov 26, 2025, at 3:25 PM, Christoph Pieper <[email protected]> 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. That you 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. Keep in 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 relates two persons with a specific type of relationship including half sibs, step sibs, uncle/aunt - whatever your users wish to tell you

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Schema design: user account deletion vs. keeping family tree data
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox