public / sequelize

* node-mysql2 install

* fixed geom, buffer and connection error handling

* disconnect connections gracefully

* switch work

* typeCast is global now, removed comment

* use mysql promise wrapper

* use sequelize's Promise instance

* used domains to catch errors properly

* parse named timezones for mysql

* return null when BLOB is empty

* use connection event emitter errors, why I didnt think about it earlier :(

* using connect fix introduced in mysql2@rc9

* handshake phase event cleanup

* need refer defined before using them

* use latedef flag with const

* [ci skip] Changelog entry

https://greenkeeper.io/

Also, fixed mssql tests

identifier has '.' should always be quoted

Reverted removeColumn value changes

(docs) #4768 Add schema examples for migrations

(docs) #4768 Add schema examples for migrations

https://greenkeeper.io/

The origin test rely on the record insert order which makes the result randomly
Fix the test

this change makes it possible to initialize Sequelize with a DSN that contains a password which contains one or more ":" characters, e.q.

```js
const Sequelize = require('sequelize')
const instance = Sequelize('mysql://root:234*%25%26%23%24%5E%40%23%7B%7D::\'.%26%40%40@localhost:3600', {});
```

in this example the MySQL password would be: `234*%&#$^@#{}::'.&@@`

without this change Sequelize attempts to connect to MySQL with a password of `234*%&#$^@#{}` ... this is a truncated password that results in a failed connection.

* Added ids to

* Removed extra added newline.

Also correct the section about promises to sound more nice.

Also `fieldName` and `freezeTableName` is nice features, but not something you need in a getting started guide. It just makes it look more complicated.

I even think that the `pool:` option in "Setting up a connection" should be removed, because who needs that anyways when they are first getting started? I could make new people think that they need it.

* added unsigned zerofilled decimal support for MySQL

* changelog for missing decimal unsigned support

* simplify code and statements

New integration test for grouped limit with schemas.

let, const, arrow functions, method shorthands, exports

instead of _.extend and _.clone

* Primary key should be same as unique key

If not, a primary key for taggable_id is created, so no more than one tag per taggable could be created.

* Define id

If not, a primary key for taggable_id is created, so no more than one tag per taggable could be created.

* fixes msssql only error when no order by but has offset or limit present

* added a test for my fix

* removed unneeded if & used proper quoteTable method for mssql only fix

* map the fieldname to attribute names

* Added timestamp attributes to fields list

* use the field to generate attributes list

* check there are no fields in dataValues

Add unit test

Don't set distinct to true as a default