[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

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.

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

On Sat, Apr 11, 2009 at 1:51 PM, Hector Gomez 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" wrote: > > > Postgre

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

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" wrote: > > Postgresql v6.3.8.1 works with Ruby 1.9.1p0 and Rails 2.3.2 - my guess > > i

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

right - somewhat slow on the uptake On Apr 11, 8:28 am, "ruby.freeman" 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 > l

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

> 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

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

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. Can you tell what the actual encoding is of the database? How about setting the default? MySQL refers to this as the CHARACTER SET. For example, to set utf8 as

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

I made a bug in lighhouse to track this problems, I have some patches for mysql and for the problem with the views in a related ticket https://rails.lighthouseapp.com/projects/8994/tickets/2476-ascii-8bit-encoding-of-query-results-in-rails-232-and-ruby-191#ticket-2476-2 On Apr 6, 8:00 am, "ruby.f

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

> 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

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

On Mon, Apr 6, 2009 at 3:42 AM, ruby.freeman wrote: > > > 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 Activ

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

> 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

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

ruby.freeman wrote: > It's problem of rails, not mysql library. ActiveRecord should be > encoding-aware now Where did you get that information? Is there any workaround or patch for that problem with ActiveRecord? -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~--

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

> 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

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

On Mon, Mar 23, 2009 at 10:16 AM, Stefan La < rails-mailing-l...@andreas-s.net> wrote: > > Jeremy Kemper wrote: > > On Sat, Mar 21, 2009 at 7:52 AM, ruby.freeman > > wrote: > >> > >> when I run console with ruby 1.9.1 and rails 2.3.2, and trying to do > >> something like > >> > >> User.first.name

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

Jeremy Kemper wrote: > On Sat, Mar 21, 2009 at 7:52 AM, ruby.freeman > wrote: >> >> 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

[Rails] Re: mysql encoding with rails 2.3.2 and ruby 1.9.1

On Sat, Mar 21, 2009 at 7:52 AM, ruby.freeman wrote: > > 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? The mysql driver is not encoding-