Code

Opened 8 years ago

Closed 6 years ago

#1374 closed enhancement (wontfix)

Add MultiObjectPaginator, which can paginate across different types of objects

Reported by: adrian Owned by: nobody
Component: Tools Version:
Severity: trivial Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: yes
Needs tests: yes Patch needs improvement: no
Easy pickings: UI/UX:

Description

I've had this lying around for the past couple of months. Pasting it here because I don't have time to continue working on it.

This introduces a MultiObjectPaginator class, which is like ObjectPaginator but paginates across different types of objects. For example, if paginating across books and CDs, it would take care of displaying books first, then CDs (or vice versa, depending on the ordering preference), and it would handle pagination properly.

Attachments (1)

paginatorNEW.py (4.1 KB) - added by adrian 8 years ago.
Unfinished implementation of MultiObjectPaginator

Download all attachments as: .zip

Change History (7)

Changed 8 years ago by adrian

Unfinished implementation of MultiObjectPaginator

comment:1 Changed 7 years ago by SmileyChris

  • Triage Stage changed from Unreviewed to Design decision needed

Is this going anywhere, adrian?

comment:2 Changed 7 years ago by russellm

  • Triage Stage changed from Design decision needed to Accepted

Its safe to assume that if Adrian opened it originally, the idea has been accepted.

comment:3 Changed 6 years ago by PJCrosier

  • Has patch set
  • Needs documentation set
  • Needs tests set

comment:4 Changed 6 years ago by adrian

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

The new Paginator class from [7306] handles this.

comment:5 Changed 6 years ago by SmileyChris

  • Resolution fixed deleted
  • Status changed from closed to reopened

From a skim through of the new paginator stuff, I can't see that it fixes this yet.

The trick is we want to be able to check the combined length of the multiple querysets without actually causing them to all be iterated (otherwise we could do a simple iter.chain).

comment:6 Changed 6 years ago by adrian

  • Resolution set to wontfix
  • Status changed from reopened to closed

Closing because the use-case is pretty rare.

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.