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

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

From: Bernice Southey <[email protected]>
To: Christoph Pieper <[email protected]>
Cc: [email protected]
Subject: Re: Schema design: user account deletion vs. keeping family tree data
Date: Mon, 24 Nov 2025 13:17:53 +0000
Message-ID: <CAEDh4nz_cKNGg0yX8k0yigZM8Ww=vcpv-0m_vMyR0je+5Kzm4Q@mail.gmail.com> (raw)
In-Reply-To: <CAEzggP_UOGwe5BA9s3iLY3R8LEi4QztA=2ka+vkRp-Wy64vXdQ@mail.gmail.com>
References: <CAEzggP_UOGwe5BA9s3iLY3R8LEi4QztA=2ka+vkRp-Wy64vXdQ@mail.gmail.com>

Christoph Pieper <[email protected]> wrote:
> Question:
> From a PostgreSQL point of view (database best practices, data integrity, performance and long‑term maintainability at millions of rows), which approach would you prefer, or is there a better pattern for this kind of “account can be deleted, but genealogy should remain” use case?

I can tell you what I'm doing. It solved many design problems, but I
don't claim it's "best practice". I split my table in two.
    1 - columns that I can keep indefinitely
    2 - personal data
That way I just delete the personal data row when I want to remove it.

Thanks, Bernice

view thread (7+ messages)  latest in thread

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: <CAEDh4nz_cKNGg0yX8k0yigZM8Ww=vcpv-0m_vMyR0je+5Kzm4Q@mail.gmail.com>

* 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