mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
9cdd0a1fdf
`add_reference` can very helpfully add a multi-column index when you use it to add a polymorphic reference. However, the first column in the index is the `id` column, which is less than ideal. The [PostgreSQL docs][1] say: > A multicolumn B-tree index can be used with query conditions that > involve any subset of the index's columns, but the index is most > efficient when there are constraints on the leading (leftmost) > columns. The [MySQL docs][2] say: > MySQL can use multiple-column indexes for queries that test all the > columns in the index, or queries that test just the first column, the > first two columns, the first three columns, and so on. If you specify > the columns in the right order in the index definition, a single > composite index can speed up several kinds of queries on the same > table. In a polymorphic relationship, the type column is much more likely to be useful as the first column in an index than the id column. That is, I'm more likely to query on type without an id than I am to query on id without a type. [1]: http://www.postgresql.org/docs/9.3/static/indexes-multicolumn.html [2]: http://dev.mysql.com/doc/refman/5.0/en/multiple-column-indexes.html |
||
|---|---|---|
| .. | ||
| change_schema_test.rb | ||
| change_table_test.rb | ||
| column_attributes_test.rb | ||
| column_positioning_test.rb | ||
| columns_test.rb | ||
| command_recorder_test.rb | ||
| create_join_table_test.rb | ||
| foreign_key_test.rb | ||
| helper.rb | ||
| index_test.rb | ||
| logger_test.rb | ||
| pending_migrations_test.rb | ||
| references_index_test.rb | ||
| references_statements_test.rb | ||
| rename_table_test.rb | ||
| table_and_index_test.rb | ||