Yaşar
Thanks .. the "using" kw hadn't occurred to me but I don't know of any
others. I'm happy now. I figure the force_* kwargs were probably the
only ones then and it wasn't too difficult for example code to mention
them. I prefer the *args, **kwargs version anyway. It hides the gory
detail
Absence of **kwargs would cause problems if for example save method is
called with "using" keyword argument. You could either list all the
available keyword arguments or use **kwargs.
By the way, is there any other kwarg for save?
2011/8/16 Mike Dewhirst
> When using save() in a model, what is
Thanks DR
Mike
On 16/08/2011 6:10pm, Daniel Roseman wrote:
On Tuesday, 16 August 2011 08:21:24 UTC+1, Mike Dewhirst wrote:
When using save() in a model, what is the difference between ...
save(self, force_insert=False, force_update=False) or
save(self, force_insert=False, force_up
On Tuesday, 16 August 2011 08:21:24 UTC+1, Mike Dewhirst wrote:
>
> When using save() in a model, what is the difference between ...
>
> save(self, force_insert=False, force_update=False) or
> save(self, force_insert=False, force_update=False, **kwargs)
> # whatever
> super(Xyz, self).sav
4 matches
Mail list logo