3
100%
master: 100%

Ran 19 Apr 2016 06:40AM UTC

Files 3

Run time 0s

Badge

Embed ▾

Committed 19 Apr 2016 06:39AM UTC coverage: 99.275% (+0.01%) from 99.265%

Job # 2.1.5, POSTGRESQL_DB_USER=postgres MYSQL_DB_USER=travis, gemfiles/activerecord-4.2/Gemfile.sqlite3

Build Type

Pull #39

travis-ci

Committed by

dmeranda

Commit Message

Only call the column's case_sensitive? if it is determined by the collation.

When determining whether a uniqueness validation should be case insensitive,
we only want to consider the column's own reported case-sensitivity if it
is a true property of the column, i.e., due to its collation/character set.

The schema_plus_columns gem monkey patches in its own version of
case_sensitive?, for PostgreSQL, that determines this based upon the
properties of ANY indexes in which the column participates. That
method does NOT correctly take into account the index scope.  Since in
PostgreSQL it is possible to have a column participate in two indexes,
one being case-sensitive and another being case-insensitive, it is
important to always consider the scope.  This does not matter with MySQL.

Pull Request Pull Request #39: Support case-insensitive uniqueness validations under MySQL

Run Details

137 of 138 relevant lines covered (99.28%)

80.41 hits per line

SchemaPlus / schema_validations / 121 / 3
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 121.3 (2.1.5, POSTGRESQL_DB_USER=postgres MYSQL_DB_USER=travis, gemfiles/activerecord-4.2/Gemfile.sqlite3)

SchemaPlus / schema_validations / 121 / 3 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 121.3 (2.1.5, POSTGRESQL_DB_USER=postgres MYSQL_DB_USER=travis, gemfiles/activerecord-4.2/Gemfile.sqlite3)

SchemaPlus / schema_validations / 121 / 3
100%
master: 100%

README BADGES
x