[Straw-devel] Article history

[Iain McCoy]

Hey folks,

I've been doing a little work on an article history feature. The basic
model that I think most sensible is that every time we store an updated
version of an article, rather than just clobbering the old one we store
it away and store the current version as well. Every change in the
article leads to one more version being stored.

The thing that I can't decide on is this: what is it about an article
that needs to be tracked throughout revisions? My current inclination is
to have article bodies be 'versioned', so to speak (with the date/time
of the article serving as a version identifier), and to clobber
everything else when it changes.

That seems to me to be the most sensible compromise between utility and
preposterous code, but it's not a decision that I'm confident about. Is
there something I'm missing?
-- 
Iain McCoy <address@hidden>