#28904 closed Bug (duplicate)
QuerySet.exclude() doesn't work properly with __in and a list containing None — at Version 2
| Reported by: | Prasad Sidda | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.8 |
| Severity: | Normal | Keywords: | __in=[None], in with None |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Excluding query with __in condition by providing [None]` as list.
Please find attachment below.
Change History (3)
by , 7 years ago
| Attachment: | Screen Shot 2017-12-06 at 4.17.12 PM.png added |
|---|
comment:1 by , 7 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 7 years ago
| Component: | Uncategorized → Database layer (models, ORM) |
|---|---|
| Description: | modified (diff) |
| Resolution: | invalid → duplicate |
| Summary: | Queryset exclude not working properly → QuerySet.exclude() doesn't work properly with __in and a list containing None |
Duplicate of #20024.
Note:
See TracTickets
for help on using tickets.
This is actually how SQL works. None will be translated to NULL and NULL compared to any value is undefined in SQL.
Closing ticket as invalid.