nice! 👍

This will need a rebase, but I know lots of people (like @schneems and @tenderlove) are pumped about supporting specific postgres types.

I'm 👍 for this feature, being able to specify types of indexes is nice definitely better than having to go in and write it manually:

  def up
    execute "CREATE INDEX products_gin_data ON products USING GIN(data)"
  end

  def down
    execute "DROP INDEX products_gin_data"
  end

I made a comment on code style, do you think you could fix that up, rebase this code, and we can get someone from ActiveRecord to take a look?

Object#method(name) is defined.

When trying to backport this to rails 3.2 it gave me a little grief.

Can we pick a different name for it?

The documentation seems to call it index_type for both postgres and my sql. While I don't like having the word index twice (IndexDefinition#index_type), it is more rails friendly than overriding Object#method.

Unfortunately, the create index code currently uses an index_type variable to specify unique. IndexDefinition uses 'unique' for this purpose, so it is only a local variable in 2 places. But a side note none the less

Thoughts?

@kbrock Maybe just type?

Heh, type sounds good. I wasn't sure if that was too vague. I'm probably overt hinking this

I notice in the mysql code, it is called :Index_type (with an uppercase i)

So, what is needed to push this forward?

@MSNexploder could you change to :type?

Totally forgot about this pull request...
Sure, I will look into it. :)

👍 I want this feature to use Trigram full text search on postgresql.

Perhaps this should be a :using option to mirror the SQL syntax.

@MSNexploder this will need to be squashed, and a CHANGELOG entry added.

Closed in favor of #9451