Based on the documentation here:
http://docs.djangoproject.com/en/dev/topics/db/managers/#controlling-automatic-manager-types
Default or Pristine managers are created for the access of related
fields on a model. It seems however that in my current version of
django (SVN-10415) that this behavior is broken.
Example:
##VIEW MODELS
class UserViewManager(ViewManager):
def get_query_set(self):
return super(UserViewManager, self).get_query_set().filter
(access__id__lte=1)
class SystemViewManager(ViewManager):
def get_query_set(self):
return super(SystemViewManager, self).get_query_set()
class View(models.Model):
objects = UserViewManager()
system = SystemViewManager()
class ApplicationSettings(models.Model):
browse_view = models.OneToOneField(View, null=True,
limit_choices_to={'owner__id': 0}, default=1, )
AppSettingsForm = modelform_factory
(app_models.LeadApplicationSettings)
The query that is generated when displaying the form is as follows:
SELECT ... FROM [view table]
WHERE ([view table].`access_id` <= 1 AND [view table].`owner_id` = 0)
Notice that the access_id restriction from the manager set to objects
is being used.
To me this behavior seems incorrect according to the docs, as it
should be using the pristine manager which selects ALL related
objects. And at present I don't have a way to work around this since I
don't think I can specify a queryset in the one-to-one field.
I have tried setting "use_for_related_fields = True" to the
SystemManager just as a wild guess but that didn't help, as I expected
it wouldn't.
Thoughts?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
