public / sequelize

* Ignore model-level validation when creating join table for n:m associations.

When declaring a join table with the through option declared as a
string, Sequelize creates the through model at runtime, and copies the
model validation rules from the source table into the through model. More
often than not, the model validation rules from the source table would be
inappropriate/undesirable for the join table (since their data fields are
different anyway).

It's also worth noting that if a through model is given, this behavior
is not exhibited.

* Added unit test for issue #5556.

http://greenkeeper.io/

http://greenkeeper.io/

Add custom validation function testcases

Fix changelog

Refactoring and more tests

Tests fix

Refactoring once more and tests fix

Unnecessary check removed

Tests fix once more

* change validate to return null on success as per the docs
* update integration tests to use null for validation success

Add example about foreign key

remove dependency on wellknown in favor of terraformer-wkt-parser

Tests for #3534, values modified in validate hooks are saved

This adds tests for the following custom validation functions:
- attribute validation functions
- simple model validation functions
- model validation functions which return a promise

fix limit=0 issue

format

replace double quotes to pass jshint

fix copy past mistake

adjust postgres tests for limit 0 and offset 0

use != null to check if limit and offset option exist

get rid of limitExist and offsetExist var

remove string test for limit and offset option

fix style

Before connection hook

bluebird@3.3.4

babel-core@6.6.5

moment-timezone@0.5.3

Update generic-pool to version 2.4.2 🚀

Add issue and PR templates

Inspired by https://github.com/nodejs/node

[ci skip] Minor Docs fix

Use transaction when creating index

Model.destroy: add model to options

Performance improvement for #3414