Code

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#13882 closed (fixed)

exclude on nullable fields uses an overly complex internal representation

Reported by: Alex Owned by: nobody
Component: Database layer (models, ORM) Version: 1.2
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation:
Needs tests: Patch needs improvement:
Easy pickings: UI/UX:

Description

It nests Where clauses more than is necessary, and this can be trivially fixed.

Attachments (1)

django-orm-exclude-null.diff (834 bytes) - added by Alex 4 years ago.

Download all attachments as: .zip

Change History (3)

Changed 4 years ago by Alex

comment:1 Changed 4 years ago by russellm

  • Resolution set to fixed
  • Status changed from new to closed

(In [13456]) Fixed #13882 -- Removed an unnecessary nested where clause introduced on isnull queries. Thanks to Alex Gaynor for the report and patch.

comment:2 Changed 4 years ago by russellm

(In [13457]) [1.2.X] Fixed #13882 -- Removed an unnecessary nested where clause introduced on isnull queries. Thanks to Alex Gaynor for the report and patch.

Backport of r13456 from trunk.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.