Re: Schema design: user account deletion vs. keeping family tree data - Mailing list pgsql-general

From Bernice Southey
Subject Re: Schema design: user account deletion vs. keeping family tree data
Date
Msg-id CAEDh4nz_cKNGg0yX8k0yigZM8Ww=vcpv-0m_vMyR0je+5Kzm4Q@mail.gmail.com
Whole thread Raw
In response to Schema design: user account deletion vs. keeping family tree data  (Christoph Pieper <christoph@fecra.de>)
Responses Re: Schema design: user account deletion vs. keeping family tree data
List pgsql-general
Christoph Pieper <christoph@fecra.de> wrote:
> Question:
> From a PostgreSQL point of view (database best practices, data integrity, performance and long‑term maintainability
atmillions 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



pgsql-general by date:

Previous
From: Michał Kłeczek
Date:
Subject: Re: set role command
Next
From: Dominique Devienne
Date:
Subject: Re: set role command