#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 |
------------------------------------+---------------------------------------
Comment (by dcotruta):
I do see what you're trying to say, but you must admit that in many cases
serialization is used to carry out trivial synchronization. In those
cases, it makes sense to be able to implement the normal save behavior -
indeed it would be doubly useful to be able to use new attributes like
force_insert since they would throw pk errors "for free" - a very easy way
of preventing data overwrites.
Just because you can create your own save function doesn't mean the built
in one should fail to support standard attributes available everywhere
else.
I'm not submitting this bug just for the fun of it, but because
force_insert is a rather unusual call which happens to be very useful when
handling over-the-wire object movement.
--
Ticket URL: <http://code.djangoproject.com/ticket/12685#comment:9>
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.
