Re: Inconsistent pagination when sorting by non-unique columns (ticket 34251)

We had a similar issue in table views, where users can highly customize the output (like switching on/off columns, complex filtering and custom multilevel ordering). For the ordering issue at hand the solution was to append the pk as n-th order directive on the queryset, if all previous

Re: Inconsistent pagination when sorting by non-unique columns (ticket 34251)

to the pagination documentation. I don't think warnings would work, because as soon as you get a "false-positive" users would simply filter/ignore the entire warning which would hide actual positives, but I guess it's better than nothing. To sum up: -1 on implicit pk ordering by

Re: Inconsistent pagination when sorting by non-unique columns (ticket 34251)

t to > be the product's stocking number; when looking at items by store, the final > parameter needs to be both stocking number and store. There wouldn't seem > to be -any- meaningful "always right" answer. > > We have something like 20,000 tests running today (and

Re: Inconsistent pagination when sorting by non-unique columns (ticket 34251)

ike 20,000 tests running today (and will probably hit 40,000 over time), many of which do pagination and sorting. I'd really, really hate to have to go fix all of those tests -- it would be thousands of them. If there was a way to disable this proposed warning, I could live with that for a w

Inconsistent pagination when sorting by non-unique columns (ticket 34251)

As described in https://code.djangoproject.com/ticket/34251, some database backends (incl. PostgreSQL) will produce non-deterministic ordering when sorting by columns with non-unique values. This leads to inconsistent pagination, which I argue falls under the same category as paginating

Re: MultipleObjectMixin and Pagination

Hi Julien, I'm already involved on that ticket, the pagination issue is part of what's holding me back from contributing a patch. So I was looking to get some discussion about whether it's something that needs to be solved in core. In light of what you've said, I'm trying to think of a more

Re: MultipleObjectMixin and Pagination

much of the existing > functionality as possible, but I've hit a bit of a snag. > > I've a ModelFormSetMixin which extends MultipleObjectMixin, much like > how ModelFormMixin extends SingleObjectMixin in core. > > I want to take advantage of the pagination that MultipleObjectMixin

Re: Tests for generic views' pagination

On Tue, Jul 6, 2010 at 4:36 PM, Julien Phalip <jpha...@gmail.com> wrote: > On Jul 6, 5:54 pm, Russell Keith-Magee <russ...@keith-magee.com> > wrote: >> On Tue, Jul 6, 2010 at 1:43 PM, Julien Phalip <jpha...@gmail.com> wrote: >> > Hi, >> >>

Re: Tests for generic views' pagination

On Jul 6, 5:54 pm, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Tue, Jul 6, 2010 at 1:43 PM, Julien Phalip <jpha...@gmail.com> wrote: > > Hi, > > > I'm starting to work on ticket #2367 ("Pagination for date based > > generic views" -http

Re: Tests for generic views' pagination

On Tue, Jul 6, 2010 at 1:43 PM, Julien Phalip <jpha...@gmail.com> wrote: > Hi, > > I'm starting to work on ticket #2367 ("Pagination for date based > generic views" - http://code.djangoproject.com/ticket/2367) and I'm > looking into the object_list generic view a

Tests for generic views' pagination

Hi, I'm starting to work on ticket #2367 ("Pagination for date based generic views" - http://code.djangoproject.com/ticket/2367) and I'm looking into the object_list generic view as a reference. For the life of me I cannot find any tests for object_list's pagination. Am I missing

Re: pagination django

Just a quick thought (though I also think the question should have been asked on the Django-Users mailing list). The template tag {% cycle %} allows you to alternate between any number of values everytime it is encountered, so putting something like : {% for product in product_list %} // a

Re: pagination django

This is a question more suited for django-users as this mailing list is for the development of the core framework. -justin On Mar 25, 2009, at 6:15 AM, nicemira wrote: > > please friends, > how can I paginate my product with this method: I want to do a newline >

pagination django

please friends, how can I paginate my product with this method: I want to do a newline after every two products please,answer me as soon as possible --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django

Re: Proposal: Generic Pagination

On 8/27/07, Iapain <[EMAIL PROTECTED]> wrote: > > > http://www.djangosnippets.org/snippets/378/ > Not really > > > http://www.djangosnippets.org/snippets/394/ > bit closer (should have used query string ?p=1 instead of /page/1) > I definitely wrestled with this. I ended up going without the

Re: Proposal: Generic Pagination

> http://www.djangosnippets.org/snippets/378/ Not really > http://www.djangosnippets.org/snippets/394/ bit closer (should have used query string ?p=1 instead of /page/1) But still I prefer the way django.contrib.admin is doing. The core question is it should be included in django standard

Re: Proposal: Generic Pagination

On 8/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Something like this? > > http://www.djangosnippets.org/snippets/378/ > I extended a different snippet to do what I wanted. Posted it just now at [1]. I do think that this needs to be looked at, for my first django project, this was one

Re: Proposal: Generic Pagination

Something like this? http://www.djangosnippets.org/snippets/378/ On Aug 27, 9:48 am, Philipp Keller <[EMAIL PROTECTED]> wrote: > +1 > > I also looked into django.contrib.admin for that > thing and wanted to reuse the code there but ended in coding it myself. > > greets > Philipp > > On Mon,

Re: Proposal: Generic Pagination

+1 I also looked into django.contrib.admin for that thing and wanted to reuse the code there but ended in coding it myself. greets Philipp On Mon, Aug 27, 2007 at 08:40:45AM -, Iapain wrote: > > Introduction: > > Most of the time ObjectionPaginator server incomplete functionality >

Proposal: Generic Pagination

Introduction: Most of the time ObjectionPaginator server incomplete functionality because some one have to generate a page bar[] in template. However some a kind of template tag would allow you to create a small tiny hack but not a generic one. I just looked inside django.contrib.admin and I

Re: reverse pagination be made default?

On 7/23/07, Tom Tobin <[EMAIL PROTECTED]> wrote: > > This assumes pagination is always done on date-sorted items; there are > plenty of other uses for pagination (e.g., splitting up a very long > list of books, sorted alphabetically by title). I *really* wouldn't > want t

Re: reverse pagination be made default?

On 7/23/07, Tom Tobin <[EMAIL PROTECTED]> wrote: > > > On 7/22/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > > I have just uploaded a patch for what I call "reverse pagination". > Please > > read about it here: > > http://code.djangoproject.com/

Re: reverse pagination be made default?

On Monday 23 July 2007 01:54:19 Amit Upadhyay wrote: > Hi, > > I have just uploaded a patch for what I call "reverse pagination". > Please read about it here: http://code.djangoproject.com/ticket/4956. > You can see it in action on my blog: http://www.amitu.com/blog/. I'

Re: reverse pagination be made default?

On 7/22/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > I have just uploaded a patch for what I call "reverse pagination". Please > read about it here: > http://code.djangoproject.com/ticket/4956. You can see it > in action on my blog: http://www.amitu.com/blog/.

reverse pagination be made default?

Hi, I have just uploaded a patch for what I call "reverse pagination". Please read about it here: http://code.djangoproject.com/ticket/4956. You can see it in action on my blog: http://www.amitu.com/blog/. The following will make sense after you have read the patch etc. I was tryin

Re: Disable admin pagination completely: discussion for ticket #4027

On May 1, 5:20 pm, Marek Kubica <[EMAIL PROTECTED]> wrote: > The current situation is a little bit annoying, with newforms-admin being > nearly ready and oldforms-admin getting unsupported. Yeah, it would be good if newforms-admin could be merged asap. I assume it's just the edit_inline

Re: Disable admin pagination completely: discussion for ticket #4027

Hello Ben, On Mon, 30 Apr 2007 16:49:57 +0700, Ben Ford wrote: > I wrote a patch a while back that implemented a 'number per page widget' for > admin. It never really went anywhere as it needed a better patch and some > tests, which I didn't have the time to supply. I don't know if you would >

Re: Disable admin pagination completely: discussion for ticket #4027

the patch. Regards Ben On 30/04/07, Marek Kubica <[EMAIL PROTECTED]> wrote: > > > Hi all, > > I created a new ticket with the need to disable pagination in the admin > object listing altogether. The current default value for pagination is 100 > objects per page, whic

Disable admin pagination completely: discussion for ticket #4027

Hi all, I created a new ticket with the need to disable pagination in the admin object listing altogether. The current default value for pagination is 100 objects per page, which can of course be extended to sys.maxint and is surely enough but this leaves an odd feeling. In the ticket I put up

Pagination for date based generic views (#2367)

Hi, I have attached a new patch to ticket 2367 to add pagination capabilities to date based generic views. I'd appreciate if someone interested could give feedback. Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: Pagination

Hi Mike, In case you are interested, I wrote a ticket that (in addition to adding some other paginator functionality) provides a PaginatorPage object which is a wrapper for a specific page. http://code.djangoproject.com/ticket/2093 I just updated it to provide some useful properties:

Re: Pagination

Malcolm Tredinnick wrote: > I'm not sure those functions make sense in the current ObjectPaginator > implementation. The thing is, that object doesn't even have a concept of > "current page". Instead it's an object from which you can retrieve any > individual page (random access) and get

Re: Pagination

On Sat, 2006-08-12 at 03:00 -0700, Mike Cantelon wrote: > I'm starting to play with Django and liking it... > > One thing I was wondering, though, about the pagination object is why > django/core/paginator.py doesn't have get_next_page and > get_previous_page functions (to return

Pagination

I'm starting to play with Django and liking it... One thing I was wondering, though, about the pagination object is why django/core/paginator.py doesn't have get_next_page and get_previous_page functions (to return the appropriate page numbers), although it does have has_next_page