pull down to refresh
100 sats \ 5 replies \ @WeAreAllSatoshi 3 Apr \ parent \ on: Perpetual Edits? meta
Also, @ek is gonna blow up the DB with his edits ;)
Yeah this could be difficult to scale. Depending on how it's implemented it might also require a compound primary key on items because their id alone would no longer identify them.
I haven't looked into the diff approach much, but that'd be minimally invasive by comparison. I just don't have experience with it.
reply
Yet another approach I think that might be the goldilocks (no need for a compound primary key on "Item") is the history table pattern1:
- 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