For those of you luddites out there still grasping to the usage of standard pagination, your mind has been made up for you. Pagination has been removed from core Rails and future reliance on it will require the installation of the classic_pagination plugin. So what’s one to do now for your pagination needs? Why, will_paginate, of course.
What's New in Edge Rails: No More (conventional) Pagination
Posted by ryan
at 7:51 AM
on Monday, June 11, 2007
Hey Ryan, don’t forget of Paginator gem ;-)
Not as magical as will_paginate, but works with find_by_sql queries (also, general purpose ruby code, not just Rails)
BTW, your blog is a good reading everytime :-)
I’ve got a question concerning all the “What’s New in Edge Rails”-posts. Is there an estimate time when these changes will be published in a stable version? I’m not talking about a current date or time, but I would like to know if these changes are more likely to appear in a 1.2.X or 2.0 version of Rails.
I would have to use the latest trunk to make use of these changes, is that right?
Following Ralph’s question… I was told by an elder statesman of Rails that it’s no longer kosher to deploy on Edge despite all of last year’s blog posts advising users to do just that. If Edge is only intended for use by Rails core [as was stated by said spokesman], then why tell us all about the goodies we’re not supposed to be enjoying?
Also, I’d like to submit Alex Wolfe’s Paginating Find for the academy’s consideration. ;) I’ve been using it for several projects and can’t imagine using anything else.
RSL, you must have misunderstood or the statesman must have been bad at explaining. What you shouldn’t do is float on edge. Meaning pull down the latest version of edge every time you deploy. But you can totally use edge for real applications if you don’t mind paying closer attention to the development process.
What you do is get the latest version of Rails, then freeze your application to that version, say 6695. Now you have a version of Rails that you can verify that your application works with. And you can then, later, move to a newer version and certify that too.
DHH, thank you for explaining that. I’ve actually been doing that [via piston] but it’s good to know I wasn’t completely insane for doing so. Every time I piston update I make sure all my tests pass. There’s nothing like a good set of tests to ensure your app can handle any changes. :)