[development] Requiring node revisions

David Strauss david at fourkitchens.com
Fri Jun 8 12:29:00 UTC 2007

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 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: OpenPGP digital signature
Url : http://lists.drupal.org/pipermail/development/attachments/20070608/fb535646/attachment.pgp 

More information about the development mailing list