Opened 15 years ago
Closed 15 years ago
#12514 closed (fixed)
Wrong Model.save() signature in topics/models and ref/models/instance
Reported by: | Armando Pérez Marques | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | ||
Cc: | mandx@… | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
With the new multi-db option, now Model.save() takes the adittional parameter 'using' specifying what DB connection to use to save the object. But in the docs, it stills shows this: Model.save([force_insert=False, force_update=False]). I realize of this because I have some models with the save() method redefined, and when updated Django to trunk version, it starts complaining about an extra keyword parameter, 'using'. I temporarily solved this using my_model.save(self, *args, kwargs), but it would be nice not to use this magic syntax.
Change History (2)
comment:1 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in [12118].