#8990: Cannot save objects when using extra() in default manager
---------------------------------------------------+------------------------
Reporter: miracle2k | Owner: nobody
Status: new | Milestone: post-1.0
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* stage: Unreviewed => Accepted
Comment:
This is actually just a symptom of a much larger problem; pretty much all
custom managers are inappropriate to use for saving. Ultimately it comes
down to using "default manager" for something that isn't really
appropriate, but a lot of people are doing that.
It's fairly tricky to fix the root problem properly (since there are some
very rare cases like GeoManager that do need to be involved, possibly),
but I'm working on it.
--
Ticket URL: <http://code.djangoproject.com/ticket/8990#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 django-updates@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
