@anon
sign up
@anon
sign up
pull down to refresh
21 sats
\
2 replies
\
@k00b
3 Apr
freebie
\
parent
\
on: Perpetual Edits?
meta
Yet another approach I think that might be the goldilocks (no need for a compound primary key on "Item") is the history table pattern
1
:
create an "OldItem" table using
inheritance
with a foreign key reference to "Item".id
on edits, copy the current "Item" to "OldItem" (taking care with primary keys and timestamps) and then edit the "Item" as usual
Footnotes
https://www.reddit.com/r/PostgreSQL/comments/kt1agc/what_is_the_best_way_of_implementing/
↩
write
preview
reply
100 sats
6 sats
hot
recent
top
0 sats
\
1 reply
\
@nym
3 Apr
What do you think about allowing reposting of old good posts, but at a considerable markup to make the repost?
reply
6 sats
\
0 replies
\
@k00b
3 Apr
I'm always interested in increasing evergreenness of old content, but I'm not sure how to do it yet.
reply
Footnotes