I have not contacted upstream (tmtm) but he is working on a pure ruby
adapter called ruby-mysql (is encoding aware, etc) it has a compat
layer but is
not functional now.
I have made a gem of my fork hectoregm-mysql-ruby that you
use to make tests, but I will try to get this changes merge upstream.
On Apr 11, 5:31 pm, Conrad Taylor <conra...@gmail.com> wrote:
> On Sat, Apr 11, 2009 at 1:51 PM, Hector Gomez <hector...@gmail.com> wrote:
>
> > ruby.freeman have you checked my fork of mysql-ruby? and the ticket
> > in lighthouse?
> > I think this will resolve your problem.
> > Or have you checked it out and still got problems?
>
> > On Apr 11, 1:28 pm, "ruby.freeman" <ruby.free...@gmail.com> wrote:
> > > > 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 #<Encoding:ASCII-8BIT>.
> > > If I do this one - User.first.name.force_encoding("utf-8") - I'm
> > > getting normal utf-8 string. The problem is that ActiveRecord gets all
> > > data from database as ASCII.
>
> Is your update forked back into the main branch for the project?
>
> -Conrad
--~--~---------~--~----~------------~-------~--~----~
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 email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
