public / sequelize

As discussed on IRC. Also add task for 2.0 to change the validate()
output structure.

The existing but unused (as far as I could tell) DAO option `validate`
can now have member methods which will be called with the model object's
context after the other (field-specific) validations.

Only custom functions are allowed (since isInt etc wouldn't make sense
in this context).

As with other custom validations, they are deemed to pass if they throw
no error, or fail if an error is thrown.

Any error messages collected are added to a '_' member array of the
validation result object, alongside the arrays named after any fields
whose validations failed.

Example:

	var Pub = Sequelize.define('Pub', {
		name: { type: Sequelize.STRING },
		address: { type: Sequelize.STRING },
		latitude: {
			type: Sequelize.INTEGER,
			allowNull: true,
			defaultValue: null,
			validate: { min: -90, max: 90 }
		},
		longitude: {
			type: Sequelize.INTEGER,
			allowNull: true,
			defaultValue: null,
			validate: { min: -180, max: 180 }
		},
	}, {
		validate: {
			xorCoords: function() {
				if ((this.latitude === null) === (this.longitude === null)) {
					throw new Error('Require either both latitude and longitude or neither')
				}
			}
		}
	})

In this simple case an object fails validation if latitude or longitude
is given, but not both. If we try to build one with an out of range
latitude and no longitude, `raging_bullock_arms.validate()`, might
return

	{
		'latitude': ['Invalid number: latitude'],
		'_': ['Require either both latitude and longitude or neither']
	}

A test is included.

SQLite addQuotes is not correct

Enable the override of the default attributes

Provide a link to a live sandbox environment where sequelizse examples are available

…mysql dialect query generator

Promises/A Support

add test for skipping validations when value is null and allowNull is true

Issue #629: Attribute ambiguity issue when eagerly loading.

make changes in issue #629 pass.

can now prepend table names to attributes. This fixes
issue #629.

Include no longer overwrites attributes in find (thanks to @mekanics)

Added options when using connection string

… options can be passed as second parameter.

…rraflubb-nowhere_is_empty

Added failing MySQL tests for SelectQuery when the `where` is all kinds of empty.
Now it returns `1=1` if nothing else, as suggested by @muka.

Properly process booleans in MySQL dialect to fix #607

… terraflubb-make_binary_verbose