Changes between Initial Version and Version 1 of Ticket #19193


Ignore:
Timestamp:
Oct 26, 2012, 1:40:59 PM (12 years ago)
Author:
Łukasz Rekucki
Comment:

Option 1 is highly backwards incompatible and option 2 looks like an API bloat - passing save=False and calling instance.save() does exactly the same and avoids potential kwargs naming conflict.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #19193

    • Property Triage Stage Unreviewed → Design decision needed

  • Ticket #19193 – Description

    initial v1  
    1 django.db.models.fields.FieldFile:
     1`django.db.models.fields.FieldFile`:
    22
     3{{{
    34def save(self, name, content, save=True):
    45....
    … …  
    67        self.instance.save(update_fields=[self.field.name])
    78....
     9}}}
    810
    911or:
    1012
     13{{{
    1114def save(self, name, content, save=True, **kwargs)
    1215....
    … …  
    1417        self.instance.save(**kwargs)
    1518....
     19}}}
    1620
    1721So, we get rid of re-saving fields when updating
Back to Top