public / sequelize

add `.original` property to custom Error classes

The current `.parent` property is a bit of a misnomer. `.original`
better conveys the intent of the field and function of the class, which
is to wrap the original database error.

This commit does not remove the current `.parent` property for backwards
compatibility.

Resolving multiple hasMany cascades which weren't working in some cases

… are not made for hooks:true #2746

…aints are not supported. #2736

linted and cleaned hooks.test.js

Use ec2 instance in us-west-1

Sequelize.close should close all connections once pool is being drained

Fixed a few misspelled words

Fixing "error: syntax error at or near ")"" when using upsert with postgres dialect

When trying to insert values containing the character `)`, the RegEx is not modifying the string properly, throwing this error message: `error: syntax error at or near ")"`.

Here's an example:

Initial value:
`VALUES ( \'Current Generator(s)\',\'CurrentGenerators__c\',NULL,NULL,\'Lead\',\'2014-12-10 22:31:24.076 +00:00\',\'2014-12-10 22:31:24.076 +00:00\');`

Current result:
`SELECT \'Current Generator(s\',\'CurrentGenerators__c\',NULL,NULL,\'Lead\',\'2014-12-10 22:31:24.076 +00:00\',\'2014-12-10 22:31:24.076 +00:00\');`

Expected result:
`SELECT \'Current Generator(s)\',\'CurrentGenerators__c\',NULL,NULL,\'Lead\',\'2014-12-10 22:31:24.076 +00:00\',\'2014-12-10 22:31:24.076 +00:00\';`

This commit is removing the `replace()` method called. After reading the blog post referred, there's no explanation of why this need to be replaced - and it is working fine without it.

Feature/mssql dialect

findAndCountAll empty include error fixed.

…com/sequelize/sequelize/pull/2697)

There have been many many little changes to the codebase during
the development of the mssql dialect that are no longer needed, as
well as missed imports of changes upstream. This realigns the
disperate trees, and fixes a few related bugs

There was some refactoring on attributes test where mssql dialect
branching was missed. Also added databaseVersion support for mssql
dialect

temporarily disable on update foreign key constraints, mssql dialect
now passes all current test cases

Major overhaul of the createTableQuery to bring it closer in line
with the mysql dialect. This closes a number of failed cases where
things were being created in a strange manner, as well as let's us
do away with SqlGenerator once and for all

These tests must be disabled since MSSQL simply doesn't allow
the updating of these types of fields. Cascading updates are supported
and should be covered by other tests.