public / sequelize

…and also checking the actual type of error thrown.

…ted from the connection failure.

As pointed out in the [PR](https://github.com/sequelize/sequelize/pull/2576#issuecomment-63018736) for this functionality we would ideally not be checking error messages and instead be checking the constructors of the objects to make sure that they are an instance of the correct error type. There's some issues right now with two different constructors being used and not being able to use `instanceof`. We could fall back to the constructor name or some other check, but at the end of the day that isn't really any better than just checking the message.

…aren't breaking up the grouping.

…o use the new errors.

…MySQL to utilize these errors.

Prefer index name when mapping unique constraint errors

unique constraint error

Undestroy method for paranoid models

update/clean readme

- update some of the links
- change h3 to h2 for sections
- add disclaimer about runnable not being up-to-date
- change twitter link to @SequelizeJS instead of @sdepold

When using migrations to create indexes instead of sync or when unique
index name has fields with underscores (was problem at least with
postgres implementation) then it was not possible to set custom error
message, because mapping the error thrown from database always failed.
Fixed by using indexName always for mapping the error if possible.

keep original error message when wrapping in DatabaseError

Add support for 'IS NULL' comparison

Allow removing has-many associations by id

#2338 - Associations remove[AS][plural]

Use pg-hstore for improved hstore handling

Use the new beta build env on Travis

caching is enabled
faster vms
faster boot times
(docs coming soon)

fixes #2521