Django，自定义管理器会影响保存方法吗？(Django, Custom Managers affect save method?)

 我正在使用Django 1.7。 我有一个默认的自定义管理器，可以过滤“活动”布尔字段。 根据文档，它需要是使用相关字段的默认管理器（即访问User.story_set仅显示活动的Story对象）。 我保留了管理员和shell访问的标准管理器，但我无法保存对象的更改，我猜测因为save（）方法在某些时候通过默认管理器。 
 
class Story(models.Model):
    active = models.BooleanField(default=True)
    ....

    objects = ActiveStoryManager()
    full_set = models.Manager()

class ActiveStoryManager(models.Manager):
    def get_query_set(self):
        return super(ActiveStoryManager, self).get_query_set().filter(active=True)
    use_for_related_fields = True
 
 这适用于所有面向公众的用途。 但是，在admin和shell中，我无法影响非活动对象，包括将它们恢复为活动状态。 
 
 story = Story.full_set.get(id=#)将获取一个active=False的故事，但在设置active=True我无法保存，得到一个 
 
 django.db.utils.IntegrityError: duplicate key value violates unique constraint "stories_story_pkey" DETAIL: Key (id)=(#) already exists. 
 
 调用save.(force_update=True)返回django.db.utils.DatabaseError: Forced update did not affect any rows. 
 
 因此，虽然save（）是一个模型方法，但它似乎依赖于保存过程中某个时刻的默认管理器。 
 
 解决方法是使用Queryset API，例如Story.full_set.filter(id=#).update(active=True) ，但这只能在shell中使用，并且需要手动键入每个更改，仍然无法保存非活动实例管理员。 
 
 对此有何帮助？ 

I'm using Django 1.7. I've got a default custom manager that filters on an "active" boolean field. According to the docs, it needs to be the default manager to work with related fields (ie. accessing User.story_set only shows active Story objects). I'm keeping the standard manager for admin and shell access, but I am unable to save changes to objects, I'm speculating because save() methods pass through the default manager at some point. 
 
class Story(models.Model):
    active = models.BooleanField(default=True)
    ....

    objects = ActiveStoryManager()
    full_set = models.Manager()

class ActiveStoryManager(models.Manager):
    def get_query_set(self):
        return super(ActiveStoryManager, self).get_query_set().filter(active=True)
    use_for_related_fields = True
 
This works well for all public-facing use. However, in admin and shell I am unable to affect inactive objects, including turning them back active. 
 
story = Story.full_set.get(id=#) will fetch a story with active=False, but after setting active=True I am unable to save, getting a 
 
django.db.utils.IntegrityError: duplicate key value violates unique constraint "stories_story_pkey" DETAIL: Key (id)=(#) already exists.
 
Calling save.(force_update=True) returns django.db.utils.DatabaseError: Forced update did not affect any rows.
 
So while save() is a model method, it seems to depend on the default manager at some point in the saving process. 
 
A workaround is using the Queryset API, e.g. Story.full_set.filter(id=#).update(active=True), but that's only usable in the shell, and requires manually typing each change, still can't save inactive instances in the admin. 
 
Any help on this?

原文：https://stackoverflow.com/questions/27085886