#10432: Empty generator in "in" lookup gives incorrect SQL
---------------------------------------------------+------------------------
Reporter: Anossov | Owner: mtredinnick
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: sql where
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* owner: nobody => mtredinnick
* needs_better_patch: => 0
* status: new => assigned
* needs_tests: => 0
* needs_docs: => 0
Comment:
That patch doesn't look like it's patching the right thing: it looks too
deep in the code. I notice that this bug is somehow specific to a
generator being used in the example, since using a list comprehension (or
any other sequence) does't demonstrate the problem.
For next time, too, a test case is definitely required in a patch for
anything like this. After all, we need to make sure it doesn't reoccur for
any reason.
--
Ticket URL: <http://code.djangoproject.com/ticket/10432#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
