Spoksss,
I brought this up as a BUG? subject and got some traction from
Malcom. Malcom opened a tracking ticket to get it fixed.
I was able to work around it by sending some querysets to my view
before, instead of using the related sets in the view. If you'd like
to see my work around, please
Hello,
I have the same problem with entry_set in my related_manager.
On 8 Lis, 05:32, John M <[EMAIL PROTECTED]> wrote:
> DR,
>
> Now I have a new problem. When I use this as a related_manager
> (Report.objects.all()[0].task_set.accomplishments()) it returns all
> the accomplishments. I've eve
DR,
Now I have a new problem. When I use this as a related_manager
(Report.objects.all()[0].task_set.accomplishments()) it returns all
the accomplishments. I've even added the use_for_related_fields=True
in the manager. The all() (default) call seems to work fine, but the
others done.
Any ide
Dave,
Thanks for the quick reply, yea, I figured out what I needed to do,
which turns out just what you said.
I will change to the pythonic way of doing things, thanks.
John
On Nov 7, 11:47 am, Daniel Roseman <[EMAIL PROTECTED]>
wrote:
> On Nov 7, 7:13 pm, John M <[EMAIL PROTECTED]> wrote:
>
>
On Nov 7, 7:13 pm, John M <[EMAIL PROTECTED]> wrote:
> I wanted to get some feedback on how I'm using custom model managers.
>
> I've put all my queries into one manager, each in a different method.
> Is this the right way to go?
>
> So for example:
>
> CHOICES_TASK = (
> (
I wanted to get some feedback on how I'm using custom model managers.
I've put all my queries into one manager, each in a different method.
Is this the right way to go?
So for example:
CHOICES_TASK = (
("NO", "None"),
("GR", "Green"),
6 matches
Mail list logo
