> Postgresql v6.3.8.1 works with Ruby 1.9.1p0 and Rails 2.3.2 - my guess
> is the problem is with either the driver or the database itself.
Problem is not with database. As I said above, when I do something
like User.first.name.encoding I'm getting #.
If I do this one - User.first.name.force_enco
> Which requests do you perform in the rails console?
any find request, like in first message
--~--~-~--~~~---~--~~
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 rubyonra
> Where did you get that information?
> Is there any workaround or patch for that problem with ActiveRecord?
See, when I do some requests from rails console, I see that result is
in utf-8 encoding, so mysql works correctly. But ActiveRecord sets
encoding for all attributes as ASCII-8BIT. For now
> Your question should also be posted to driver maintainers and possible the
> MySQL and SQLite projects. Furthermore, all these projects are open-source.
> Thus, please feel free to contribute/add these features if you need them.
It's problem of rails, not mysql library. ActiveRecord should be
the solutions is that now we have to set :method => :get in options,
but not in :url hash. then it works
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email t
when I run console with ruby 1.9.1 and rails 2.3.2, and trying to do
something like
User.first.name.encoding
I'm getting #, though I've set "encoding: utf8"
in database.yml
any suggestions?
--~--~-~--~~~---~--~~
You received this message because you are subscrib
no, sorry. it still doesn't work
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send
found. now I have to write '_method' instead of :_method
thanks to all
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.co
> Isn't _method only there for those methods that browsers won't use (eg
> DELETE). You should be able to make link_to_remote do an actual get
> rather than a fake one.
the question is - why rails 2.2.2 generates right JS cod for Ajax GET
request, but 2.3.2 isn't. It doesn't matter wich exactly
I also found, that :_method => :get in link_to_remote doesn't work
anymore. That is, rails 2.3.2 doesn't treat it as GET request, but as
POST. so REST route doesn't work
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
10 matches
Mail list logo
