[development] Requiring node revisions

Peter Wolanin pwolanin at gmail.com
Fri Jun 8 12:25:45 UTC 2007


A new/updated node still has to INSERT or UPDATE the {node} table, so
(maybe this is what you mean) the gain is only the code handing the
revisions, right?


On 6/7/07, David Strauss <david at fourkitchens.com> wrote:

> The real reason I'm pushing for mandatory revisions is so content types
> don't have to implement two saving mechanisms, one UPDATE, one INSERT.
> So, we should just pick one. The revisions system is the clearly
> superior choice.

More information about the development mailing list