#12685: Serialized objects' save function does not respect force_insert
---------------------------------------------------+------------------------
Reporter: dcotruta | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.1
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by anonymous):
* status: closed => reopened
* resolution: invalid =>
Comment:
Erm, I'm not asking a question, I'm stating a fact.
http://docs.djangoproject.com/en/dev/ref/models/instances/#saving-objects
states very clearly the function signature as:
Model.save([force_insert=False, force_update=False,
using=DEFAULT_DB_ALIAS])
Deserialized objects of the type I've described above, which DO NOT
override the save behavior, don't accept the force_insert keyword
argument. This is not a question - it's a bug.
Unless I'm missing something, there should be no difference in the
behavior of save for deserialized objects.
--
Ticket URL: <http://code.djangoproject.com/ticket/12685#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
