In Rails 5, the schema layer was updated so that indexes could be
created on expressions rather that simply columns. Update
`have_db_index` so that you can test for this.
More reading: <edc2b77187>
18b2859 and a0f1221 fixed the numericality matcher so that it no longer
raises CouldNotSetAttributeError when used against numeric columns.
Unfortunately, the issue still existed for money columns.
This is fixed now, but we never explicitly tested for money columns, and
this commit adds that test.
Please note that array columns do not work properly between Rails 4.0
and 4.2.
* If you set an array-of-date or array-of-time attribute to an
array, it will fail to hold that value. This is an issue with
timestamp-aware attributes and is fixed in Rails 4.2.
* Even if this worked, the uniqueness validator cannot cope with array
columns, producing an invalid query. This will be fixed in 4.1.10.
When running tests, you can now switch between running them against a
SQLite or PostgreSQL database. This is accomplished by modifying the
unit and acceptance tests so that when they generate and load the test
Rails application, database.yml is replaced with content that will
configure the database appropriately.
Elliot Winkler