public / sequelize

BigInt/Datatypes enhancements

Fixing 'identifier' being stored as the raw value of the 'id' rather than being wrapped in an object

Default ports are now declared in the ConnectorManager.

Fix belongsTo where params

…fix-belongs-to-where-params

…lude-case-insensitive

identifiers in Postgres

Continuation of a fix outlined in [pull request 656](https://github.com/sequelize/sequelize/pull/656)

Usually when adding to a `foobar.getBla()` a where param
like `foobar.getBla({where: {x: "y"}})` it should extend
the existing where param (`"id": id`) with the additional
where param.
This didn't work for belongsTo associations until now.

Fixing a bug in query generation where 'identifier' is being stored as the raw value of the 'id' rather than being wrapped in an object.

When the raw value of ```id``` is stored as ```identifier``` in ```save()``` an invalid query is returned from the ```QueryGenerator```.

i.e. - Without the fix, an UPDATE query looks like this:  
```UPDATE `Users` SET `gender`='male',`email`='updated@bar.com',`updatedAt`='2013-05-29 23:33:36',`createdAt`='2013-05-29 23:33:36' WHERE 2```  

The ```WHERE 2``` is not the desired behavior. If ```id``` is wrapped in an object then the correct query is generated:  
```UPDATE `Users` SET `gender`='male',`email`='updated@bar.com',`updatedAt`='2013-05-29 23:33:36',`createdAt`='2013-05-29 23:33:36' WHERE `id`=2```

PostgreSQL will no longer try to split regclass identifiers for default values.

Added special field for describing tables with Postgres, this will give us ...

findOrCreate returns additional flag to tell whether the entry was found or created