store deleted data in a separate place (table or file) instead of in-place soft delete #7

New issue

Open

opened 2022-07-21 23:11:48 +02:00 by MoralCode · 3 comments

MoralCode commented

2022-07-21 23:11:48 +02:00

Owner

See https://brandur.org/soft-deletion for the reasons why.

The main reason i added soft deletion was in case users accidentally deleted something important and missed the timeout window provided by react-admin.

See https://brandur.org/soft-deletion for the reasons why. The main reason i added soft deletion was in case users accidentally deleted something important and missed the timeout window provided by react-admin.

MoralCode commented

2022-10-10 04:08:18 +02:00

Author

Owner

it seems as though that article is based on/written for Postgres databases. Im not sure if jsonb columns exist in MariaDB (what classclock uses).

another alternative is to just make a copy of every table and have that be for deleted data, or maybe have a separate instance of the DB?

Should probably reach out to the author to see if they know of any concrete implementations of this strategy in the wild (i.e. other open source projects).

it seems as though that article is based on/written for Postgres databases. Im not sure if `jsonb` columns exist in MariaDB (what classclock uses). another alternative is to just make a copy of every table and have that be for deleted data, or maybe have a separate instance of the DB? Should probably reach out to the author to see if they know of any concrete implementations of this strategy in the wild (i.e. other open source projects).

MoralCode commented

2022-10-10 17:42:29 +02:00

Author

Owner

since mariaDB does not have JSON columns (according to https://mariadb.com/resources/blog/json-with-mariadb-10-2/) another option may be best to just export the data for deleted columns into a series of JSON files in a directory in a format that can potentially be re- imported into the admin panel later if needed