We don't need to check whether the table exists or whether the slug field is present on the translated model as this is documented and will fail later on.

I'm removing it because this check invokes ActiveRecord too early which plays havoc with asset precompilation.
Prepped 4.0.4 release
replace 'joins' with 'includes', because joins causes record to be readonly
Merge pull request #258 from schiza/patch-1

Replace 'joins' with 'includes'

Joins causes record to be read-only
added test and fix using translations.reload for dynamic finder results from friendly_id.
add globalize3 to gemfile for testing
move globalize3 dependency to gem specification.
refactor and add test (for translated slugs using globalize).
Merge pull request #264 from shioyama/reload_translations

test and fix using translations.reload for dynamic finder results from translated slug using globalize
Bumped version
Add globalize3 to ci Gemfiles
Postgres can order differently so we shouldn't check for absolute equality but that the contents are correct. This fails before the tap patch and passes after it.
Adding note to NOT add uniqueness constraint on scoped slug's column in the database.
Merge pull request #266 from asanghi/patch-1

Adding note to NOT add uniqueness constraint on scoped slug's column in ...
Set version date

[ci skip]
Merge branch 'master' of github.com:norman/friendly_id
Remove Gemfile from .gitignore
If there is no error in friendly_id attribute then #move_friendly_id_error_to_name removes any existing error from the name attribute.
Merge pull request #285 from nolamesa/patch-1

Move_friendly_id_error_to_name example method removes errors on name field
Fix reserved words example

See pull request #285.