[development] Use revisions to replace previews
bashratthesneaky at gmail.com
Fri Jun 8 15:35:45 UTC 2007
On Jun 8, 2007, at 16:34 , Morbus Iff wrote:
>> Not only that, but I have visions of a database full of trivial or
>> identical node revisions. For example, what if the user changes
>> only the
>> taxonomy selections and then previews the node? All those DB
>> queries and
>> extra data in the table, for nothing. Or they change a bit of HTML
>> and preview, trying several times to get it just right. The user
>> may have
>> only worked for a couple of minutes, so what's the value in
>> preserving all those
> This is pretty much the way I work - I could easily spend 30
> previews before I finish what I consider my first draft of a node.
> I would hate to waste 30 revisions (and the overhead) for stuff
> like that.
That's why it was suggested to automatically delete revisions that
were used for previews. Not that it would become elegant code, but
that would at least get rid of the overhead.
More information about the development