Greg Plesur wrote: > But I would _not_ expect to see this: > >>> x=SomeModel.objects.all() # This gets a QuerySet into x > >>> value = x[0] # Some operation to actually fill x's cache > >>> print len(x) # Verify that there are some entries in the table > 2 > <perform an external operation, delete all rows from SomeModel's table> > >>> y=SomeModel.objects.all() # This gets a new QuerySet into y > >>> value = y[0] # Some operation to actually fill y's cache > >>> print len(y) # The new QuerySet has the cached result from x! > 2 > > It's the second that I'm seeing - with the result that I can't get at > fresh data once any QuerySet in my process has fetched the data once.
I don't see this using a checkout of Django from yesterday. May be this was a bug and it's fixed. Another possibility is that both you processes work in different transactions and it's why they don't see what each other does in the DB. Though if you indeed do this under shell it shouldn't be the case since there you should start a transaction manually. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
