migrations: t.references doesn't allow index name to be specified

Question

I have the following in a migration:

create_table :model_with_a_long_name do |t|
  t.references :other_model_with_an_equally_long_name, index: true
end

That produces an index with too long of a name for Postgres.

Is there a way to manually specify the index name (without adding the integer column and the index separately)?

Something like the following:

create_table :model_with_a_long_name do |t|
  t.references :other_model_with_an_equally_long_name, index: true, index_name: 'model_and_other'
end

?

Possible duplicate of [How do I handle too long index names in a Ruby on Rails ActiveRecord migration?](https://stackoverflow.com/questions/5443740/how-do-i-handle-too-long-index-names-in-a-ruby-on-rails-activerecord-migration) — Jon Schneider, Jan 04 '19 at 00:00

score 140 · Accepted Answer · edited Jul 25 '18 at 10:16

140

According to Rails code for references, you can do so, providing index a Hash with options, the one you need called :name, so:

t.references :my_field, index: { name: 'my_index_name' }

edited Jul 25 '18 at 10:16

chobo

answered Feb 25 '15 at 19:48

Rustam Gasanov

2

I love Rails, so simple! – Rafael Oliveira Mar 11 '16 at 01:52
The order threw me off. I had index at the very end before null and foreign key. thanks! – Gustavo Matias Apr 30 '22 at 00:25

score 1 · Answer 2 · edited May 26 '22 at 05:23

1

Specify it longhand:

  t.integer :othermodel_id
  ...
end
add_index :thismodel, :othermodel_id, name: 'othermodel_index'

edited May 26 '22 at 05:23

Community

answered Feb 25 '15 at 19:44

Eric

2 Answers2