Overriding save() raises error when using Model.objects.create()

[pjs]

It seems that when over writing .save() (and maybe other default methods) you should be accepting *args, kwargs and passing it along.

I get an exception when using Model.objects.create():

Traceback:
File "/usr/local/lib/python2.5/site-packages/django/core/handlers/base.py" in get_response

86. response = callback(request, *callback_args, callback_kwargs)

File "/home/pjs/site/netlandish/../netlandish/ccproc/views.py" in order_process

41. form_data.get('custom', )

File "/home/pjs/site/netlandish/../netlandish/billing/helpers.py" in build_sale

48. ip=ip

File "/usr/local/lib/python2.5/site-packages/django/db/models/manager.py" in create

87. return self.get_query_set().create(kwargs)

File "/usr/local/lib/python2.5/site-packages/django/db/models/query.py" in create

311. obj.save(force_insert=True)

Exception Type: TypeError at /order/1027/
Exception Value: save() got an unexpected keyword argument 'force_insert'

My custom .save() didn't have anything catching force_insert..

The docs don't show this is required.

[Julien Phalip]

This is probably a side-effect due to [8673].

[Malcolm Tredinnick]

This is a docs bug. We should mention the need for force_insert and force_update if you want your overridden method to be usable by create() or get_or_create(). It's in the BackwardsIncompatibleChanges page, but I forgot to update the docs.

[Malcolm Tredinnick]

(In [8689]) Fixed #8662 -- Fixed the documentation of Model.save() to match the real
signature so that people overriding it will use the right signature.

[James Tauber]

typo in the doc, see #8759

[x_O]

Docs here ​http://www.djangoproject.com/documentation/models/save_delete_hooks/
are still in old version, this produces a lot of confusions.

[Jacob]

Milestone 1.0 deleted