Hi,
The current implementation of CurrentSiteManager only 'spans' one
model. For example, take the following code:
class Foo(models.Model):
[...]
site = models.OneToOneField('sites.Site')
on_site = CurrentSiteManager("site")
class Bar(models.Model):
[...]
foo = models.ManyToManyField(Foo)
What I would really want is to do the following:
class Bar(models.Model):
[...]
foo = models.ManyToManyField(Foo)
on_site = CurrentSiteManager("foo__site")
, and have it "just work" by jumping through the 'foo' field onto the
'site' field on the Foo model.
We currently have that code written. Is it worth turning that into a
patch for contrib.sites, with unit tests et al, and pushing upstream
into django? Should I fill out a bug?
Thanks in advance,
--Rory Geoghegan
--
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers?hl=en.
