#12685: Serialized objects' save function does not respect force_insert
------------------------------------+---------------------------------------
Reporter: dcotruta | Owner: nobody
Status: reopened | Milestone: 1.2
Component: Serialization | Version: 1.1
Resolution: | Keywords: save, force_insert,
force_update
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by ramiro):
* stage: Accepted => Unreviewed
Comment:
Replying to [comment:3 dcotruta]:
> The problem is that the call to save_base in core/serializers/base.py
within the class DeserializedObject does not have the capability to carry
through the correct signature.
Exactly, and this (the existence of !DeserializedObject, the fact that its
save method isn't the same as the Model save method, and that you need to
provide your own logic to decide if a !DeserializedObject instance should
be saved or not) is intended and documented (in the documentation that
should be read in first place: The one about (de)serializing) behavior:
http://docs.djangoproject.com/en/1.1/topics/serialization/#deserializing-
data
--
Ticket URL: <http://code.djangoproject.com/ticket/12685#comment:8>
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.
