I just fixed this. I was on a heroku stack that had unicode issues (bamboo-mri-1.9.1 (beta)) I'm not having problems after migrating to bamboo-ree-1.8.7.
On Jun 26, 12:21 am, JL <jlee.j...@gmail.com> wrote: > I'm having encoding problems on heroku, where I can't fetch unicode > from the database. > > I've setup a simple program following the steps in the first demo > in:http://rubyonrails.org/screencasts(except I use postgres instead of > sqlite) > > So my site has some pages that are just barely more than scaffolds > with two or three text input fields. > > Everything works fine on my local machine. > On heroku, everything works as long as the text fields only have ASCII > characters. > If any of the text fields contain multibyte (unicode) characters, the > page won't load on heroku. > > Has anyone had a similar problem? > Thanks! > > <<<<This is how I setup my database.yml file>>>> > production: > adapter: postgresql > encoding: unicode > database: blog_production > pool: 5 > username: postgres > password: zzz > > <<<<Here's the relevant portion of the heroku log>>>>> > Processing ApplicationController#show (for 1.1.1.1 at 2010-06-26 > 00:04:14) [GET] > Parameters: {"id"=>"6"} > > ArgumentError (invalid byte sequence in US-ASCII): > <internal:prelude>:8:in `synchronize' > /home/heroku_rack/lib/static_assets.rb:9:in `call' > /home/heroku_rack/lib/last_access.rb:25:in `call' > /home/heroku_rack/lib/date_header.rb:14:in `call' > thin (1.2.6) lib/thin/connection.rb:76:in `block in pre_process' -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
