There is one huge problem with 1.9 and it is how it manages encodings. Sure every ruby fanatics will tell you that it is “cleaner”, “more robust”, “safer”, “clever” or whatever… but it breaks working applications! So in my book this is a problem. I know it is just normal to refactor some aspects of your code when a new version of a programming language comes out but… this? All this pain for what, encodings? What’s the benefit already? No seriously tell me because I wake up every morning having to remember what they are, what purpose they serve and why application developers still have to worry about them after all those years. What I know however is that with 1.8 you could mix different encodings in the same string instance and the worst that could happen was some weird looking characters in the resulting web page. But ruby 1.9 makes things different, it throws an exception in your face. Here is a great article that explains what is happening with string encodings in 1.9. Beware though, although this article is saying that there is a solution, it is an hypothetical solution. Here is the excerpt :

Even better, Ruby already has a mechanism that is mostly designed for this purpose. In Ruby 1.9, setting Encoding.default_internal tells Ruby to encode all Strings crossing the barrier via its IO system into that preferred encoding. All we’d need, then, is for maintainers of database drivers to honor this convention as well.

So, unless I’m just not getting something (which is highly possible because encodings always confuse the heck out of me), there is no real solution other than to wait for database driver developers to honor the Encoding.default_internal setting of ruby 1.9.

A small rant about encodings
I dream of a world without war or hunger and where I don’t have to care about character encodings when I’m programming! Why on earth do we have all those different encodings in 2010? Why not making a huge encoding table UTF-16384 containing every single character in the universe so we can forget about this crazy concept of different encodings and pretend that it never existed? Would a big fat and unique encoding table cause huge performance issues everywhere? I might be mistaken but I really doubt it would.

For the past few months this blog has been pretty much dead. I could give you tons of excuses as for why it has been so but that’s all they would be, mere excuses! And I assure you that you would not find any of them very convincing.

I received several comments recently telling me that you liked my blog and asking me when I plan writing again and believe me, it always goes straight to my heart. For some time now I am in the expectation that most of you will give up on me and remove this blog from your list forever but for some reason… you don’t!

Since I am a bit rusty at writing blog posts, I chose the easy way : a numbered list of Rails Gems/Plugins that I like. Hmmm, I know… it’s soooooo 2007! But, interesting nonetheless. If you don’t mind, I’d like that you share in the comment section the plugins that you like the most as well. Perhaps this post could become a reference to discover great plugins. Oh btw, from now on I will use the terms plugins and gems like they were the same thing.

1. Paperclip by Thoughtbot

   Very easy to install & configure. I use it for thumbnails generation and it works wonder.

2. locale_routing by Perfectline

   If you are developing a multilingual app/website (with I18n), don’t miss this simple plugin. It auto inserts the locale in the url without messing with your routes.

3. thinking-sphinx by freelancing-gods

   A fast and reliable free-text search solution for your rails apps, using the Sphinx daemon. The only thing that is really unfortunate with sphinx is that is doesn’t index new database records live out of the box. Instead you have to build the index manually or setup a cronjob at a given interval. The workaround is to use delta indexes with the delayed-job plugin but it forces you to have a rake task always running on your server. I had so much problems with the rake task getting killed for no apparent reason that I decided that live indexing was not so important. Instead I have a cronjob running every X hours that rebuild the index from scratch

4. will_paginate by mislav

   I guess we all know and use this one but I had to put it in my list anyway. It is such a great and easy to use pagination plugin.

5. acts_as_state_machine by rubyist

This one I use all the time. Everytime an activerecord object can be in more than a single “state” (enabled, hidden, locked, whatever)… think about using it!

That’s it! Now, it’s your turn : what is your own top 5 list?

The following is a guest post from Dan Simard

Sometimes, you have to reinvent the wheel. It’s really sad to say and you will probably hate me for saying that (and I know that you’ll do because I hate myself for it). I’ve written a new globalization plugin for Rails.

Why did I reinvented the wheel?

I searched and tried a lot of other globalisation plugins… and I really tried them. I spent hours with Globalize. It was just too much. I tried the gettext_Localize that works with the good ol’ gettext command. Fuck it. Too complicated. It just didn’t fit my needs at all.

All I wanted was a wheel that you can put a wood-pole in the middle and then it could start spinning. I made one.

You can go on the simplyglobal project homepage to learn on to install it and use it.

In fact, this is not really a globalization plugin because there’s no localization handling or anything that can look like it. The name should have been simplytranslated but I already created the project with the name simplyglobal and it was an hassle to change it.

How to install

1. Execute ./script/plugin install http://simplyglobal.googlecode.com/svn/trunk/simplyglobal
2. Create a file named simplyglobal.rb in the config/initializers directory
3. In simplyglobal.rb, create hashes of language
Add the language hashes to the objectYou will end up with a file named simplyglobal.rb that looks like this :

In development, this file will be loaded every request. In production, it is loaded once.

How to use it with strings

After you installed it, you can use it in these various ways.

SimplyGlobal adds a t() method to all string objects that will return the translated string. Example, if you have defined a language hash that looks like this (note : normally, the languages hash are defined in config/initializers/simplyglobal.rb but I put it inline for the sake of the example) :

As simple as that!

You can use it like the % method of the String class.

You can also return all translations for a word. That is a special feature developed only for Frank.

Using it with views

Just create a view ending with _fr and simplyglobal will use it.

It also works for the partial.

will try to render _info_fr.html.erb rather than _info.html.erb.

Fortunately, version 0.4 has been released on August 5th 2008. We’re going to try this new version internally and eventually use it for TimmyOnTime. I am personnally hoping for less memory consumption, more speed and more stability. This new version highlights are :

1. The beginning of ruby 1.9 support
2. Refactoring of error classes (I’m really looking forward to this)

Here is the full changelog :

XMPP4R 0.4 (05/08/2008)
=======================
* Initial support for Ruby 1.9 (see README_ruby19.txt)
* Complete PubSub API Change – more logical and better for
childclasses, support for collection node creation
* a Helper to assist with XEP-0115 Entity Capabilities
* SASL anonymous support
* File transfer fixes
* MUC room configuration fixes
* initial support for XEP-0118 User Tune
* fix for an xmlrpc exception-during-serialisation bug, which would cause
a hang
* Support auto-gem generation on GitHub with improved and DRY’er RakeFile and
gemspec.
* Add support for the old SSL protocol (needed to connect to GTalk)
* Changed API for Client, Component, Connection, Stream to remove
need for antiquated ‘threaded’ param in the initializer.
* Use a Logger instance instead of directly writing to stdout
* Re-factored & consolidated Error classes. See xmpp4r/errors.rb for all
custom errors that can be caught. All inherit from Jabber::Error which
itself inherits from Ruby’s StandardError. This is a first step in
re-factoring errors. The next step will be to convert all ‘raise’ calls to
raise a custom Jabber::Error or one of its children instead of anonymous
RuntimeErrors. This allows much more granularity in catching and handling
errors later.
If you were catching Jabber::ErrorException before you should probably
change that in your code to now catch Jabber::Error if you want to
catch everything or one of the custom children of Jabber::Error defined in
‘lib/xmpp4r/errors.rb’. Additionally, the Error class which encapsulated
the xmpp error response, has been renamed to ErrorResponse to reflect its
real usage. This free’s up ‘Jabber::Error’ for use as our base Error class.

gedit is great… but it is rather limited features-wise. Recently I have tried Komodo Edit and I can say that this is the best RubyOnRails editor available on Linux. It has a lot of features (autocomplete, tons of supported languages, macros, color schemes, etc) but somehow it is still light and minimalist.

Komodo Edit is also available on Mac and Windows

I think it is something related to Rails that makes me so excited. I just tried deploying a rails application with Phusion Passenger (aka mod_rails)… and I am still shocked. Rails deployment has finally becomes a breeze! At the time I am writing this, I still have this exaggerated dumb smile in my face expressing my satisfaction… and I am alone in my house.

#UPDATE : I removed the smiling pig image that was put here to “express my satisfaction”. I removed it because it was not funny and it made me look like someone who is not funny… which is something I am not comfortable with. Now that I have removed the image of the smiling pig, I expect to receive my first comment (and tons of others) for this blog post. For those who liked the smiling pig, you can find it here and pretend it is funny.

Ok enough stupidities, Phusion Passenger is great. It is built to work with the Apache web server. No port configuration, no complicated vhost configuration, you upload your stuff and guess what? It works. Well, almost… to restart your rails application you just have to touch tmp/restart.txt. If you’re using capistrano, it means that you only have to do something like that :

And what about the vhost configuration?

<VirtualHost *:80>
ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /home/you/apps/yourapp/current/public
</VirtualHost>

I didn’t have time to play with all the settings and read the documentation… but I have the feeling that this thing is the light, try it!


gem install passenger
passenger-install-apache2-module


Our hate towards the SQL language and databases is not a valid excuse to not assume our responsabilities as application developers. Recently I was working on a Rails plugin when the sentiment of being incompetent struck my body exactly like the lightning strikes an adventurous golfer who happily plays golf during a thunderstorm.

It all happened when I had a query that was generating a lot of results… and was slow as hell to process… even though I was using the :include option for Eager Loading.

@stuff = ParentStuff.find(:all, :include => :child_stuff, :order => “created_at DESC”)

Then, in my view, I had something like :

It was awfully slow! I started looking at the logs and saw this typical monstruous sql query. Look at it… you have to look at it. I know you don’t want to… but it won’t go away :

SELECT parent_stuff.`id` AS t0_r0, parent_stuff.`field1` AS t0_r1, parent_stuff.`field2` AS t0_r2, parent_stuff.`field3` AS t0_r3, parent_stuff.`field4` AS t0_r4, child_stuff.`id` AS t1_r0, child_stuff.`field5` AS t1_r1, child_stuff.`field6` AS t1_r2, child_stuff.`field7` AS t1_r3, child_stuff.`field8` AS t1_r4, child_stuff.`field9` AS t1_r5, child_stuff.`field10` AS t1_r6, child_stuff.`field11` AS t1_r7 FROM parent_stuff LEFT OUTER JOIN child_stuff ON child_stuff.the_foreign_key = parent_stuff.id WHERE (parent_stuff.created_at >= ‘2008-04-24 00:00:00′ AND parent_stuff.created_at <= '2008-04-24 09:44:56') ORDER BY parent_stuff.created_at

What's the problem with this? It's just one query... cannot take that much time. I thought it was a "Rails problem" until I ran the query directly in a MySql web interface. It took the same amount of time, meaning that the problem was within the query itself. Oh sh**... it was a database problem! Like many Rails Developers, my database skills are, while not inexistant, inadequate.

I tried to figure out what could be the problem with this query. I replaced every LEFT OUTER JOIN with INNER JOIN and Boom! the query executed in less than half a second.

My urgent desire of leaving the MySql web interface made me go back to my Rails code. I then tried some stupid random stuff like :

@stuff = ParentStuff.find(:all, :include => :child_stuff, :joins => “INNER JOIN child_stuff ON child_stuff.parent_stuff_id=id” :order => “created_at DESC”) but the slow LEFT OUTER JOINs remain in the query instead of being replace by the faster INNER JOIN. Then, I learned that in Rails 2.0, you could do Eager Loading with INNER JOIN by passing an association name to the :joins option, like that :

@stuff = ParentStuff.find(:all, :joins => :child_stuff, :order => “created_at DESC”)

Problem is I was working on a plugin… and I’d like it to be compatible with older versions of Rails. So I did what I was scared of doing since the beginning : Going to some MySql forums to read the advice of some DBA’s …

Then I found the answer to my problem… and this answer proved me that I needed to stop playing blindly with ActiveRecord like if the backend database was none of my business…. because it is. The answer is so obvious… but given the fact that I never wanted to care about databases since Rails exists, I didn’t think about it :

Answer : Add an index to the foreign key in the child table!

This is just one case that shows the dangers of not being aware of what’s going on in the database. It’s sad, but you cannot blindly let ActiveRecord manage everything that is Database related for you. It’s only a question of being in control of the entire application… and the relational database is a part of it.

UPDATE
This post has kind of turned against me. The only thing I wanted to say with this article is that ActiveRecord needs our supervision… not that I am a moron who can’t understand databases. I know what joins are, I know what indexes are… but in most situations I don’t have to “care” about them with ActiveRecord. Sorry but I felt the need to defend myself about this issue :)

What is this? First post in a century? What’s going on here Fleebie? Our beloved readers are going to stop respecting us, and for good reasons.

For those who care, I am not dead, I am not sick… I am just working like crazy on Azanka, the company I started with Dan recently.

Ok now it’s time for a brand new edition of Rubyize this. Let’s get the ball rolling. Hold on… I’m going to google images to get a picture of a ball rolling.

Hmm… I’m afraid this isn’t going to roll at all

Anyway, consider this :

I am an old and unhappy programmer from the late eighties and you secretly watch me coding the following lines :

Bring the light to this man who retires in 2 days

Refactor this on RMC!

I just want to wish you a merry Christmas. Have a good time with your loved ones. That’s it! I’m ending this post by showing you my 2 favorite Christmas songs. What are yours?

#1 : This Jingle Bells interpretation by Frank Sinatra is simply incredible. Too bad it’s just the beginning of the song… could not find the full version on youtube. I love those J-I-N-G-L-E BELLS, Oh!

#2 : Let it snow by Frank Sinatra

Who is Mrs. Pratt?

Mrs. Pratt is a super woman who will help you remember where you things are!

The idea is simple : You tell Mrs. Pratt whenever you lend something to someone. Say for example that you lent your Bing Crosby Christmas album to Georges, you just have to tell Mrs. Pratt about it, like that :

Developed with RoR and uses xmpp4r for IM integration

Once again, this is a project I created with RubyOnRails. I also used the ruby library Xmpp4r which is the object of an ongoing serie of articles on RubyFleebie.

There is also a really simple API available for developers who would like to integrate Mrs. Pratt with their own appliaction.

That’s it! I hope you will like the idea. If you do, please be kind enough to send me your comments/suggestions/rants about the project at contact@mrspratt.com