8 Jun
2007
8 Jun
'07
2:29 p.m.
Yes. Everywhere but {node} there currently has to two save handlers, one for updates and one for new revisions. Peter Wolanin wrote:
David,
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?
-Peter
On 6/7/07, David Strauss <david@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.