On Mon, 2007-12-17 at 07:56 -0600, Tim Chase wrote: > >> This: Model.objects.filter(...).exclude(id__in = processed) > >> gives me: Truncated incorrect DOUBLE value: 'Model object' > > I've seen the above request on the ML several times now. > > Is there any hope that, in the QuerySet refactor, the "__in" form
No, since I'm not adding every single enhancement possible in that branch. You're talking about a change that requires nested sub-queries, which will be easier/possible with that code, but not something I'm going to implement immediately. It's also not a showstopper user-case in practice. Even if you do pull back 10,0000 rows, extract their id values (which you do with a .values() query the first time) and sent a second query, it isn't that bad. Databases are fast here in the 21st century. Sometimes it will be a problem, but for the majority of cases, not so much. Nice behaviour to have one day, but less important than a number of other issues. Malcolm -- Works better when plugged in. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
