Hmm, seems to work perfectly fine if I specify relate_name (but won't
work no matter what I do with just <name>_set) in M2M field as you
have.
Is this a requirement?
On Jun 26, 3:21 am, Daniel Lindsley <
polarc...@gmail.com> wrote:
> dookehster,
>
> Sorry, but I can't reproduce this one. I put together the smallest
> possible test case I could make to try to replicate this
> (
https://github.com/toastdriven/filtering- follow the
> ``README.rst``). When I run that setup, M2M filtering works for me.
> I'd recommend you poke at it then compare with your code to see where
> there are differences.
>
> Daniel
>
>
>
>
>
>
>
> On Wed, Jun 22, 2011 at 3:55 PM, dookehster <
dookehs...@gmail.com> wrote:
> > Hi, I've asked for help on IRC and was told to follow up on a post on
> > this mailing list. Basically, I was unable to get filtering on a URL
> > for a reverse relationship.
>
> > Resources:
> >
http://dpaste.com/557590/
>
> > Models:
> >
http://dpaste.com/557591/
>
> > Stack Trace onhttp://dookvm:8080/api/v1/appointment/?format=json&patients=3:
> >
http://dpaste.com/557593/
>
> > Cheers!
>
> > -Brandon