[Rails] Re: Working round 'invalid byte sequence'

2009-11-03 Thread Toby Rodwell
Matt Jones wrote: On Nov 2, 5:31�pm, Toby Rodwell rails-mailing-l...@andreas-s.net wrote: this issue? �Without being an expert in this area (obviously) I guess that either I can try to tell Ruby to treat the MySQL data as an encoding other than UTF-8 (I guess US-ASCII �but it could be trial

[Rails] Re: Working round 'invalid byte sequence'

2009-11-03 Thread Frederick Cheung
On Nov 3, 10:09 pm, Marnen Laibow-Koser rails-mailing-l...@andreas- s.net wrote: Toby Rodwell wrote: [...] Many thanks for the reply Matt.  I used the console to determine that the db is serving up ASCII-8BIT e = Equipment.find(:first, :conditions = ['id = ?', 1234]) e.name.encoding

[Rails] Re: Working round 'invalid byte sequence'

2009-11-03 Thread Marnen Laibow-Koser
Frederick Cheung wrote: [...] This is not about the database itself this is to do with the interaction between the mysql driver and the new string encoding schemes - strings in ruby 1.9 are encoding aware and from what I gather the mysql driver creates strings with the ascii-8bit encoding

[Rails] Re: Working round 'invalid byte sequence'

2009-11-03 Thread Marnen Laibow-Koser
Toby Rodwell wrote: [...] Many thanks for the reply Matt. I used the console to determine that the db is serving up ASCII-8BIT e = Equipment.find(:first, :conditions = ['id = ?', 1234]) e.name.encoding = #Encoding:ASCII-8BIT I then set the encoding in /config/database.yml to 'ascii'

[Rails] Re: Working round 'invalid byte sequence'

2009-11-03 Thread Matt Jones
On Nov 2, 5:31 pm, Toby Rodwell rails-mailing-l...@andreas-s.net wrote: I am a very amateur Rubyist who, amongst other things, likes to use a simple Rails app to query my company's MySQL config database.  The server I now use to do this has got 1.9.1 and Rails 2.3.3.  I've now hit the