On Friday 08 June 2007, David Strauss wrote:
Larry Garfield wrote:
Then maybe we should move toward having a revisions cleanup system that, by default, deletes all old revisions. It would still be a big code simplification. If the system is set to keep no old revisions, node.module can simply delete old revisions after saving the new one.
I believe I said that ~20 messages ago. :-)
If we're going to have an "always on" revision system, then it really does need to include a self-cleaning mechanism by default as well. Otherwise you have a system that takes more effort to maintain, or else never lets you delete anything. Let's not be Google.
Or maybe even my original post:
Using modules that automatically clean up old revisions can cap the increase in database size.
Sounds like we're in complete agreement then. :-) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson