3 ms·
uh, that's a really interesting idea that i've never used before -- like a graveyard for data. have you done it before? how did you implement it?
by fernandotakai 4y ago
uh, that's a really interesting idea that i've never used before -- like a graveyard for data.
have you done it before? how did you implement it?
- no_wizard 4y agoyes, I have done it, and I've implemented it two ways: A temporary "marked for deletion" (I guess temporary soft_delete) field was used to mark rows for deletion (we had a user trash type deal) anything older than 30 days just got dump into a new table, and it recorded some simple metadata, but the data itself was dumped as JSONB. The important thing is we always recorded a way to figure out the customer / user without having to dig into the JSON blob, so if they ever actually left the platform we could still delete the data in full quite easily. This was key. It preserved the PK system we had in place for stuff like this. In another, more naive implementation, we just dumped it out into JSON blobs with special "$metadata" fields describing data types, deletion time, and other associated metadata I can't quite recall. if I recall correctly those were then encrypted and stored elsewhere (I can't recall where exactly, but likely S3 or equivalent). I don't think this was a good idea, but its what was done.