Re: Impact of a CustomManager on the RelatedManager

2008-09-23 Thread bruno desthuilliers
On 23 sep, 01:26, gaz <[EMAIL PROTECTED]> wrote: > Thanks Bruno, > > I'd already tried that - I noticed that with or without the > use_for_related_field FWIW, it's a plural, ie "use_for_related_field*s*" - but I assume the typo wasn't in your code. Out of curiousity, which Django version are you

Re: Impact of a CustomManager on the RelatedManager

2008-09-22 Thread gaz
Thanks Bruno, I'd already tried that - I noticed that with or without the use_for_related_field being set on the Custom Manager the effect was the same - ie. the RelatedManager fires off it's own code without actually using the MyCurrentSiteManager instance that is already associated with the Mod

Re: Impact of a CustomManager on the RelatedManager

2008-09-22 Thread bruno desthuilliers
On 22 sep, 01:49, gaz <[EMAIL PROTECTED]> wrote: (snip) > I have overloaded the default manager in my model to use a slight > variant of the CurrentSiteManager, shown below. > (snip) > What I am seeing is that the following queries work and present only > the objects which are on the site (Venue)

Impact of a CustomManager on the RelatedManager

2008-09-21 Thread gaz
Hi everyone, I apologise for the verbosity of this message - for my first post it's quite long. I am currently working on my first project employing the Sites framework, and have been moving along quite well with the documentation until I hit a snag last night. I have overloaded the default man