> > 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 saving to x: x = mysqlTable.objects.all() y=x[0] y.assignee would always fail. Sorry to leave that out. However, if i sliced immediately, it would work: > x = mysqlTable.objects.all()[0] > x.assignee The cause is that django-pyodbc wasn't receiving the correct connection instance. I corrected that by passing it in the code listed in my original post and it works great now. > I'm not sure why "where" comes into this whole discussion, because > cross database queries aren't *ever* going to work (or, at least, they > aren't going to work without some *serious* effort). It was about three lines of code for me, no problem so far. :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
