Jordon Bedwell

I do it wrong so you can learn a new way to do it right.

Systems and Programming

Rid of those extra tables, use PostgreSQL arrays.

Rails 4 final release is nearing soon and over the last few months I’ve had the “pleasure” of playing with it in both production testing and in just standard testing and over that time I’ve accumlated a list of things that I most look forward to. I can say that I’m a little bit excited for once about a Rails release, mostly because of some of the features I’ve been using since long before Rails thought about it.

One of my absolute favorites coming into Rails 4 is the addition of “native” support for PostgreSQL arrays. To some people this can have a huge impact on how they build their code and can even simplify the management of not only that code but the tables they use. We no longer need multiple tables for tagging (not that we did before since Arrays have been in existence since I can remember.)

What I mean is, now that Rails has “native” support for PostgreSQL arrays, maybe people will start to use them more, and instead of seeing things like “skills” and “tags” in different tables we will see them on the user themselves and now instead of using flexibility as an excuse for MongoDB we will now see people use HStore instead, unless Mongo is something they actually want to use (which has to be judged on a case by case basis, I am absolutely not against MongoDB and actually use it.)

The Migration.

class CreatePosts < ActiveRecord::Migration
  def up
    enable_extension :hstore
    create_table :posts do |t|
      t.text :title, :null => false
      t.integer :author, :null => false
      t.string :tags, :null => false, :array => true
      t.hstore :ops, :null => false
      t.text :slug, :null => false

      t.index :author, {
        :unique => false

    execute "CREATE INDEX idx_tags_on_posts ON posts USING GIN(tags)"
    execute "CREATE INDEX idx_opts_on_posts ON posts USING GIN(opts)"

The migration above is just as easy as the Model below. The one thing to note here though is that unlike hstore, for a PostgreSQL array you create your type and then tell PostgreSQL it’s an array. Which means you can do it for most any type, for example: t.integer :author, :null => :false, :array => true.

The Model.

class Posts < ActiveRecord::Base
  class << self

    # --
    # @return [ActiveRecord]
    # @param [String] tag The tag.
    # Pull posts by tag.
    # --
    def with_tag(tag)
      where("? = ANY (tags)",

Just like before we got “native” support for array and HStore you must build your own helper methods. I for one do not disagree with this approach but others might, so I’ve build a basic with_tag helper. If you would like to know more ways you can query PostgreSQL please check out the documentation

The Data.{
  :title   => "Test",
  :slug    => "test",
  :author  => 1,

  :opts => {
    :publish => true

  :tags => [

# => #<ActiveRecord::Relation [
# =>   #<Posts id: 1, ..., tags: ["test"], ...>
# => ]>

And a List of Other Features I Like:

  • Russian Doll caching. Caches in my caches.
  • Strong Params. MassAssignment moved to the controller.
  • Sprockets moved to sprockets-rails, yay for updates?

Like Jekyll Talk or this article? Consider donating to our hosting bill. Donate!