public / sequelize

You can now declare unique indices like so:

var User = sequelize.define('User', {
	username: {
		type: DataTypes.STRING,
		unique: {
			name: 'username_and_email',
			msg: 'Your username and email must be unique!'
		}
	},
	email: {
		type: DataTypes.STRING,
		unique: 'username_and_email'
	},
	aCol: {
		type: DataTypes.STRING,
		unique: true
	}
})

Will create two unique indices one for username/email combo and the
other for aCol. If a unique constraint occurs for aCol, the old behavior
still occurs (emits a dialect returned error), but for username/email
index the returned error would be, "Your username and email must be
unique!"

…ithub.com/sequelize/sequelize/issues/843

Conflicts:
	lib/associations/has-many.js

Conflicts:
	lib/dao-factory.js
	lib/dao.js
	test/support.js

Basic function and trigger migrations

…ying-node-mysql-options

This commit fixes paranoid: true option, .find, .all, and .count will no...

This commit allows you to define a defaultValue for timestamp fields.

Added a test to ensure primary keys for postgres wouldn't necessarily be...

Updated depdencies.

…by paranoid's rules. This does not test for associated models with paranoid true but it's the first step.

…into a serial. Closes https://github.com/sequelize/sequelize/issues/358

Update with column

require config file to allow for json or js files