On 2/26/07, C.jay Martin <[EMAIL PROTECTED]> wrote:
>
> Actually a correction to the above statement and a partial solution.
>
> I hadn't rebooted all my services on exactly one test I did, so this is
> the truth of it:
>
> When I use the paginate command in the controller, I get the error
> -EVERY- time I create/edit/delete.  It worked fine under heavy testing
> before the migration.
> When I replace it with @region = Regions.find(:all) and -really- reboot
> all my mongrel services, it works perfectly.
>
>

AFAIK, mongrel didn't mess with Rails, but there exist lot of cases
that thigns mess up... :-P

> It seems either SQL Server, Mongrel, ISAPI Rewrite, or the Reverse proxy
> screws with some of the underlying code in paginate...I have no clue
> why, but most of my problems were resolved by taking pagination out of
> my app.
>
> I really like pagination, though...suggestions appreciated.
>

Will Paginate?

http://errtheblog.com/post/929


-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to