Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

...Paul's latest activity

Wednesday, June 23 2010
4690 Mongrel doesn't work with rails 2.3.8 was updated in Ruby on Rails
  • ...Paul
    ...Paul commented at 6:52 PM

    The simple fix natbro provided seems to have fixed the cookie issue, but redirects are still broken. Any redirect done results in page saying "You are being red...

Wednesday, May 26 2010
4690 Mongrel doesn't work with rails 2.3.8 was updated in Ruby on Rails
  • ...Paul
    ...Paul commented at 7:11 PM

    How does that solve the problem, given that I have rack 1.1.0? (Rails 2.3.8 will complain loudly if you don't have that revision...)

  • ...Paul
    • Tag changed from 2.3.8, rack to 2.3.8, mongrel_cluster, rack
    by ...Paul at 5:59 PM

    Given that I know mongrel_cluster has fallen somewhat out of favor, I decided this might be the time to check out using Nginx with Passenger. Sure enough, the a...

Tuesday, May 25 2010
4690 Mongrel doesn't work with rails 2.3.8 was updated in Ruby on Rails
  • ...Paul
    ...Paul commented at 11:52 PM

    I'm getting a similar problem. script/server works fine, all good, but when I push out to my servers which use mongrel_cluster, when setting a cookie (such as a...

Tuesday, April 06 2010
4330 databases.rake: db:dump task abuses "schema_search_path" and makes false assu... was updated in Ruby on Rails
  • ...Paul
    • Tag changed from databases.rake, pg_dump, postgresql, schema_search_path to 2.3.5, databases.rake, pg_dump, postgresql, schema_search_path
    by ...Paul at 12:49 AM
Wednesday, March 10 2010
2412 [Patch] Postgres support for standard_conforming_strings = on was updated in Ruby on Rails
  • ...Paul
    • Tag changed from 2, edge, postgres to 2, 2.3.5, edge, postgres
    by ...Paul at 12:29 AM

    Ah, this bug was already filed, great. I sparked some commentary on the wrong, bug, issue #1837, that may have some bearing. It looks like the patch is already ...

1837 PostgresSQLAdapter#unescape_bytea does not handle "\\" was updated in Ruby on Rails
  • ...Paul
    ...Paul commented at 12:21 AM

    Kurt, I think you're right. I'll file a new bug about the problem with standard_conforming_strings and Rails, and copy some of the info from this thread to that...

Monday, March 08 2010
1837 PostgresSQLAdapter#unescape_bytea does not handle "\\" was updated in Ruby on Rails
  • ...Paul
    • Assigned user set to Jeremy Kemper
    by ...Paul at 9:11 PM

    Oops, didn't mean to clear the responsible party... And I note my backslashes got eaten a bit, but I think the point is obvious.

  • ...Paul
    • Assigned user cleared.
    by ...Paul at 9:10 PM

    It's not just dropping the prefix when standard_conforming_strings is set to "on" -- it's also about checking that the Postgres lib being used (pg, postgres, wh...

  • ...Paul
    ...Paul commented at 7:28 PM

    If you can't change your database configuration, try this as an initializer:

    
    module ActiveRecord
      module ConnectionAdapters
        class PostgreSQLAdapter
         ...