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
