[patch]: Support for additional model.Field setting (update=True|False).

[Eric Van Dewoestine <ervandew@…>]

Patch based on development version 4051.

The attached patches add support for an additional model field argument (update=True|False, defaulting to True) which allows the user to mark fields which should or should not be include in any update statements made on behalf of the model.

This is especially useful if the field in question is managed via an external process (like a database trigger).

Ex.

class Poll (models.Model):
  totalVotes = models.IntegerField(default=0, editable=False, update=False)

In the above example the totalVotes column would never be included in django's update sql statement to the database.

For completeness, you may want to add a corresponding insert=True|False which applies the same rules to insert sql statements.

[Eric Van Dewoestine <ervandew@…>]

django/db/models/base.py.diff

[Eric Van Dewoestine <ervandew@…>]

django/db/models/fields/init.py.diff

[James Bennett]

This really feels like specialized behavior that should be handled in a custom save method, not in Django's core.