I'd like to jump in with a heads-up to people testing documentation they've
written or generating edge docs for themselves: while making a new template
for Rails 3 docs (porting Hanna http://wiki.github.com/mislav/hanna/ to
RDoc = v2.4) I've discovered a number of bugs in the latest RDoc release
Hi,
I fetched a forked mysql driver and got rid of this error for strings
fetched from the database.
BUT all I had to do to see this message again was to enter a non-ASCII
character in a (login) form field and there it was!
It doesn't matter that I don't even allow non-ASCII characters right
Not sure if it'll help you or not (especially since there isn't an
ActiveRecord driver yet) but my new Mysql2 gem forces the use of UTF-8
for connections to MySQL as well as strings in 1.9 -
http://github.com/brianmario/mysql2
I'll be working on and releasing an ActiveRecord driver soon, but
As I say in the subject line, it is NOT about mysql, I solved the
mysql-UTF issue already, so it won't help, sorry ;-(
On Apr 6, 8:11 pm, brianmario seniorlo...@gmail.com wrote:
Not sure if it'll help you or not (especially since there isn't an
ActiveRecord driver yet) but my new Mysql2 gem
(Rails3 latest git master)
Subject says it. I'm trying to figure out how to use erubis features
described here: http://www.kuwata-lab.com/erubis/users-guide.05.html#rails,
especially preprocessing. My question is, where do I place the
Erubis::Helpers::RailsHelper.preprocessing=true
Not in
Yeah, it seems my post started a bit misleading.
The issue is I get the error when the parameters sent to Rails from
the form look like this (look at login, which contains mörre):
Parameters: {authenticity_token=..., user={login=m
\xC3\xB6rre, password=[FILTERED], remember_me=0},
commit=...}
