*Subject:* Re: ManyToMany problem
Thanks, Tom. So, I've changed my code slightly.but I'm still getting an
error. I'm pretty much following exactly what is in the Django docs as well.
I'm wondering if it's because I have my models in different modules. That
shouldn't matter though should
Thanks, Tom. So, I've changed my code slightly.but I'm still getting an
error. I'm pretty much following exactly what is in the Django docs as well.
I'm wondering if it's because I have my models in different modules. That
shouldn't matter though should it? Maybe I'm doing something wrong with
On Thu, Sep 29, 2011 at 5:20 PM, James DeMichele
wrote:
> Thanks for the response, that's a completely inaccurate statement.
>
> Here's an example from the Django docs:
>
> https://docs.djangoproject.com/en/1.3/topics/db/models/#intermediary-manyt
> omany
>
> The Group
ubject: Re: ManyToMany problem
I don't think you can make the 'through' argument a string, and I
don't think there's circular dependency issue with the 'through'
kwarg.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
I don't think you can make the 'through' argument a string, and I
don't think there's circular dependency issue with the 'through'
kwarg.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
Thank you, it solved this problem :)
Now, I've encountered another issue, which you can see below. When
using only single item in annotation it works, but when using two, it
returns the same result.
I've added default ordering in all of my models, and as you can se,
I've tried including it
On Thu, Feb 17, 2011 at 5:01 AM, Amar wrote:
> OK, I've created a barebone app which shows this problem, so if anyone
> can try this and duplicate, I'll report this as a bug (unless there is
> a problem wih my code)
> You can get it here
OK, I've created a barebone app which shows this problem, so if anyone
can try this and duplicate, I'll report this as a bug (unless there is
a problem wih my code)
You can get it here http://rapidshare.com/files/448393624/problem.zip
I'm using PostgreSQL database, so change accordingly (unless
On Wed, May 27, 2009 at 4:18 PM, MartinBorthiry
wrote:
>
>
>
> On May 27, 6:11 pm, Alex Gaynor wrote:
> > On Wed, May 27, 2009 at 4:07 PM, MartinBorthiry
> > wrote:
> >
> >
> >
> >
> >
> > > Hello,
> >
> > > I have
On May 27, 6:11 pm, Alex Gaynor wrote:
> On Wed, May 27, 2009 at 4:07 PM, MartinBorthiry
> wrote:
>
>
>
>
>
> > Hello,
>
> > I have this model with a manyToMany relationship:
>
> > class Group(BaseClass):
> > ...
> > members =
On Wed, May 27, 2009 at 4:07 PM, MartinBorthiry
wrote:
>
> Hello,
>
> I have this model with a manyToMany relationship:
>
> class Group(BaseClass):
> ...
>members = models.ManyToManyField
> (Client ,through='Membership',related_name="members"
>
Thanks, Meir.
On Jan 7, 11:24 am, mksoft wrote:
> Hi Alex,
>
> On Jan 4, 12:27 pm, knight wrote:
>
>
>
> > Hi,
>
> > I have the following problem:
> > I have models.py with the following class:
>
> > class Section(Feed):
> > parent =
Hi Alex,
On Jan 4, 12:27 pm, knight wrote:
> Hi,
>
> I have the following problem:
> I have models.py with the following class:
>
> class Section(Feed):
> parent = models.ManyToManyField('self', blank=True, null=True)
> depth = models.IntegerField(editable=False)
>
13 matches
Mail list logo