Thanks for the suggestion, but I do that and I still see the same problem.
This is pretty weird to me, because it seems like this should work, and I'm
pretty sure I've done this in other projects and it worked just fine. I
have no idea why it's not working now.
On Sat, Jul 2, 2011 at 7:42 PM, Ja
On Sat, Jul 2, 2011 at 8:07 AM, Matthew Gardner wrote:
> a = A.objects.get(pk=some_id)
> b_set = a.b_set.select_related().all() # recommended in the Django
> documentation for some queries
> And b_set comes up empty, for some reason that I can't explain.
a.b_set isn't a QuerySet; it's a Related
Hi all,
I'm seeing some funny behavior when using select_related to try to speed up
my code, and I'm wondering if I'm just misunderstanding something.
The basics of my code:
class A(models.Model):
# some stuff
class B(models.Model):
a = models.ForeignKey('A')
c = models.ForeignKey('
passed no
arguments".. perhaps this could be reworded?)
On Jun 26, 2:18 am, phillc <[EMAIL PROTECTED]> wrote:
> yourversion of django before or after qsrf merge?
>
> select_related does not work well with relations that have null = True
>
> On Jun 24, 11:40 pm, bob84123 &
yourversion of django before or after qsrf merge?
select_related does not work well with relations that have null = True
On Jun 24, 11:40 pm, bob84123 <[EMAIL PROTECTED]> wrote:
> I'm having a problem with select_related; I'm not sure if it's a bug
> or a problem w
I'm having a problem with select_related; I'm not sure if it's a bug
or a problem with my understanding of how it's supposed to work.
Here's some code:
from django.db import models
class Occurrence(models.Model):
start_time = models.OneToOneField('Ti
6 matches
Mail list logo
