Because unfortunately innoDB tables don’t support full text searching of UTF-8 encoded content. But innoDB tables are more flexible in general. Source of information: http://dev.mysql.com/doc/refman/5.1/en/fulltext-restrictions.html and http://www.dotmana.com/?p=95. This might not be relevant, but could be.
Robert K. (or others), If you do have have the exact line for the enforce coding and in witch erb files to put it I would be happy. PS: I've tried <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> (http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/) in the top of my app/views/layout/application.html.erb I thought this would force the browser to use UFT-8. But not. I'm able to force the browser to show content after the page is read with right click- Encoding on screen (but only i just one of the string columns contains a special characters - strange). -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
