#3854: DO_NOT_SAVE_LATER after data processing from one field sets related
objects
--------------------------------------------------------------------------+-
Reporter: [EMAIL PROTECTED] |
Owner: nobody
Status: closed |
Component: Admin interface
Version: SVN |
Resolution: duplicate
Keywords: mass data entry DO_NOT_SAVE_LATER many-to-one related rows |
Stage: Design decision needed
Has_patch: 1 |
Needs_docs: 0
Needs_tests: 0 |
Needs_better_patch: 0
--------------------------------------------------------------------------+-
Changes (by ubernostrum):
* status: new => closed
* resolution: => duplicate
Comment:
Closing in favor of #5390, because that one would offer a clean solution
to this problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/3854#comment:2>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
