Re: django/db/models/sql/where.py: line 215

2011-02-07 Thread Łukasz Rekucki
On 7 February 2011 17:55, Sneaky Wombat wrote: >> >> x = mysqlTable.objects.all() >> x.assignee >> >> doesn't work, because a list of objects doesn't have an assignee. > > clearly it was a typo on my part, no need to be nasty :)  I know x is > a qs and understand its operation the way you describe

Re: django/db/models/sql/where.py: line 215

2011-02-07 Thread Sneaky Wombat
> > x = mysqlTable.objects.all() > x.assignee > > doesn't work, because a list of objects doesn't have an assignee. clearly it was a typo on my part, no need to be nasty :) I know x is a qs and understand its operation the way you describe it. What I meant was if I took an element from it AFTER

Re: django/db/models/sql/where.py: line 215

2011-02-06 Thread Russell Keith-Magee
On Thu, Feb 3, 2011 at 6:40 AM, Sneaky Wombat wrote: > I'm not sure what sort of answer this question will lead to, but here > goes. I know foreignkeys on separate databases isn't supposed to work, > according to the django docs, but I got it to work.  First off, I'm > using an old release (1, 2,

Re: django/db/models/sql/where.py: line 215

2011-02-06 Thread legutierr
I'm afraid that I can't help you with the specific problem that you are describing, but I would like to recommend that you look at the work that Waldemar Kornewald and Thomas Wanschik are doing with their django-dbindexer: http://www.allbuttonspressed.com/blog/django/joins-for-nosql-databases-via-

django/db/models/sql/where.py: line 215

2011-02-02 Thread Sneaky Wombat
I'm not sure what sort of answer this question will lead to, but here goes. I know foreignkeys on separate databases isn't supposed to work, according to the django docs, but I got it to work. First off, I'm using an old release (1, 2, 0, 'alpha', 1), one of the earlier multidb releases. Because