…::Client:: CHARSET MAP[' latin1'] = Encoding:: UTF 8
This will solve your problems in Ruby but will not solve your problems in the database: MySQL will still sort and compare strings thinking they are latin1 and thus do so incorrectly. Here's an example:
CREATE TABLE names_latin1 ( name varchar ( 32 ) character SET latin1 ) ; INSERT INTO names_latin1 VALUES ( 'Martin Strauße' ) ; INSERT INTO names_latin1 VALUES ( 'Martin Straure' ) ; INSERT …
- Article RSS Feed: April 2009 Meeting
- Programblings: Two Shoulda best practices
- On the Path: The Path to an Agile Maturity Assessment
- Effectif Development: Fixing the Xcode Project Templates
- codahale.com: The Rest Of The Story
- Lindsay Holmwood - auxesis' musings: Behaviour driven infrastructure through Cucumber
The first two bugs are important. Those using pt-archiver -bulk-insert with UTF-8 data should definitely upgrade. Those using pt-heartbeat -utc should also definitely upgrade.
Users may note the revival of the -show-all option in pt-query-digest. This had been removed in 2.2.1, but resulted in too much output in certain cases.
A new -recursion-method was added to pt-table-checksum: cluster. This method attempts to auto-discover cluster nodes, alleviating the need to specify cluster node DSNs…
UTF-8 is now the default encoding
The list of new features is more than we can cover here. If you really wanted to dig in you can check the Ruby changelog
Running 2.0 on Heroku
If you're interested in taking advantage of these new features give it a try on Heroku today. To run Ruby 2.0 on Heroku you'll need this line in your Gemfile : ruby "2.0.0"
Then commit to git: $ git add . $ git commit -m "Using Ruby …
- Giles Bowkett: Ryan Davis, You Are An Idiot, A Liar, Or A Fool
- Justin Leitgeb: Moving beyond mixins
- Headius: Explanation of Warnings From MRI's Test Suite
- The Real Adam: Reflecting on Ruby releases
- A Fresh Cup: Double Shot #1073
- igvita.com: Web Performance Power Tool: HTTP Archive (HAR)
The UTF-8 default encoding, which make many magic comments omissible
Built-in libraries
Enumerable#lazy and Enumerator::Lazy, for (possibly infinite) lazy stream
Enumerator#size and Range#size, for lazy size evaluation
#to_h, which is a new convention for conversion to Hash
Onigmo, which is a new regexp engine (a fork of Oniguruma)
Asynchronous exception handling API
Debug support
DTrace support, which enables run-time diagnosis in production
TracePoint, which …
- WyeWorks Blog - The Team's Voice: Rails 4 compilation links
- A Fresh Cup: Double Shot #1073
- Phusion Corporate Blog: Why Rails 4 Live Streaming is a big deal
- giant robots smashing into other giant robots: My wife is getting really into whiskey
- Giles Bowkett: Review: Create Your Own Freaking Awesome Programming Language
- CRAZ8: Seven Advanced Rails Fragment Cache Techniques
…Unix, Plan 9 OS, The Unix Programming Environment book, UTF-8, and most recently the Go programming language .
Waza is the Japanese word for art and technique and it's where we celebrate craft and the creative process of software development with technical sessions and interactive artistic happenings .
In planning Waza 2013 we went back to reflect on last year's speakers. And we want to make the talks readily availble to anybody who could …
- New Relic: Notes from Waza, Heroku's first developer event
- Viget.com Blogs: Around "Hello World" in 30 Days
- Invisible Blocks: After OsCon 2010
- Labnotes: Rounded Corners 357 - Tying shoe laces
- RubyLearning Blog: The Ruby movement
- Merbist: Go's reflection example
The default output encoding for RDoc is now UTF-8. Previously RDoc used the default external encoding which was determined from your locale. Issue #106 by Justin Baker.
RDoc:: RI::Store is now RDoc::Store so ri data generated by RDoc 4 cannot be read by earlier versions of RDoc. RDoc:: RI::Store exists as an alias of RDoc::Store so ri data from older versions can still be read. RDoc:: RI::Store will be removed in RDoc 5.
Tests that create RDoc:: CodeObjects on …
- A Fresh Cup: Double Shot #1073
- Tender Lovemaking: RDoc on your iPad
- Codeshooter's Weblog: Setting up your Ruby on Rails application in an Ubuntu Jaunty Jackalope (9.04) server with Nginx, MySQL, Ruby Enterprise Edition
- Nikos D.: Google Summer of Code Proposal: GRuVeR: A General Ruby library for solving Routing Vehicle Problem
- Jason Seifer: Rails 3.0 rc2 Notes
- Riding Rails - home: [ANN] Rails 2.3.14
The default encoding for ruby scripts is now UTF-8 [#6679]. Some people report that it affects existing programs, such as some benchmark programs becoming very slow [ ruby-dev:46547].
Iconv was removed, which had already been deprecated when M17N was introduced in ruby 1.9. Use String#encode, etc. instead.
There is ABI breakage [ruby-core:48984]. We think that normal users can/should just reinstall extension libraries. You should be aware: DO NOT COPY .so OR .bundle FILES …
- A Fresh Cup: Double Shot #1073
- Global Nerdy: Developer Roundup: Penny Arcade's Glowing Review of the Surface Pro, New Releases of Ruby, Rails and CoffeeScript, and the Best
- Heroku: Matz on Ruby 2.0 at Heroku's Waza
- Coding Horror: Why Ruby?
- New Relic: Living on the Edge with Rails 4 & Ruby 2
- Practicing Ruby: Practicing Ruby's second volume now freely available
…v3.0007 which has a bug that causes Perl not to flag UTF-8 data as being UTF-8. Presuming that the MySQL table/column is using UTF-8, and the Perl MySQL connection is also using UTF-8, then a correct system returns:
PV = 0x9573840 "\343\203\213 \303\250"\0 [UTF8 "\x{30cb} \x{e8}"]
That's a Devel::Peek inside a Perl scalar variable which clearly shows that Perl has recognized and flagged the data at UTF-8. With DBD::mysql v3.0007 …
- John Resig: .nodeName Case Sensitivity
- Plataformatec Blog: Exporting data to CSV and Excel in your Rails apps
- giant robots smashing into other giant robots: This Week in Open Source
- Christy John: What is actually unicode and how Java implements it?
- Headius: Representing Non-Unicode Text on the JVM
- igvita.com: Protocol Buffers, Avro, Thrift & MessagePack
…gem we ran into some cases where the data being posted back to our controller had invalid UTF-8 bytes. For Griddler, our failing case needs to simulate the body of an email having an invalid byte, and encoded as UTF-8.
What are valid and invalid bytes? This table on Wikipedia tells us bytes 192, 193, and 245-255 are off limits. In ruby's string literal we can represent this by escaping one of those numbers: > "hi \255" => "hi \xAD"
There's …
- gnuu.org: Ruby 1.9 Encoding Issues, Again.
- Katz Got Your Tongue?: Ruby 1.9 Encodings: A Primer and the Solution for Rails
- Adventures with Ruby: Writing YAML files
- Binary Code: Ruby: Invalid multibyte char error and rspec
- Matthew Bass: Processing malformed files with FasterCSV
- p.latyp.us: PDF/Writer
The default encoding for ruby scripts is now UTF-8 [#6679] . Some people report that it affects existing programs, such as some benchmark programs becoming very slow [ruby-dev:46547] . The spec may change for the official release.
iconv was removed, which had already been deprecated when M17N was introduced in ruby 1.9. Use String#encode, etc. instead.
There is ABI breakage [ruby-core:48984] . We think that normal users can/should just reinstall …
- A Fresh Cup: Double Shot #1063
- Heroku: Ruby 2.0 Preview Available on Heroku