validation: http://sequelize.readthedocs.org/en/latest/docs/models-definition/index.html?highlight=validate

// Creating two objects with the same value will throw an error. The unique property can be either a
 // boolean, or a string. If you provide the same string for multiple columns, they will form a
 // composite unique key.
 someUnique: {type: Sequelize.STRING, unique: true},
 uniqueOne: { type: Sequelize.STRING,  unique: 'compositeIndex'},
 uniqueTwo: { type: Sequelize.INTEGER, unique: 'compositeIndex'}

sync should be false, as table creation is the duty of migration

Model.findAndCountAll({
  where: ...,
  limit: 12,
  offset: 12
}).success(function (result) {

})

http://docs.sequelizejs.com/en/latest/docs/migrations/

Project.find({ where: {title: 'aProject'} }).on('success', function(project) {
  if (project) { // if the record exists in the db
    project.updateAttributes({
      title: 'a very different title now'
    }).success(function() {});
  }
})

Tasks.bulkCreate([
  {name: 'foo', code: '123'},
  {code: '1234'},
  {name: 'bar', code: '1'}
], { validate: true }).catch(function(errors) {
  /* console.log(errors) would look like:
  [
    { record:
    ...
    errors:
      { name: 'SequelizeValidationError',
        message: 'Validation error',
        errors: [Object] } },
    { record:
      ...
      errors:
        { name: 'SequelizeValidationError',
        message: 'Validation error',
        errors: [Object] } }
  ]
  */
})

task.save().then(function() {

  // my nice callback stuff

})

 

task.save().catch(function(error) {

  // mhhh, wth!

})

OR

Task

  .build({ title: 'foo', description: 'bar', deadline: new Date() })

  .save()

  .then(function(anotherTask) {

    // you can now access the currently saved task with the variable anotherTask... nice!

  }).catch(function(error) {

    // Ooops, do some error-handling

  })

avoid setting a parameter upon using a json object from a form e.g.

 console.log(john.get({
    plain: true  // do not print sequelize additional stuff
  }))

You can also transform an instance into JSON by using JSON.stringify(instance) This will basically return the very same as values.

person.reload() will fetch the current data from the database and overwrite the attributes of the model

http://stackoverflow.com/questions/22958683/how-to-implement-many-to-many-association-in-sequelize

Creating assocations in sequelize is done by calling one of the belongsTo / hasOne / hasMany functions
on a model (the source), and providing another model as the first argument to the function (the target).

• hasOne - adds a foreign key to target
• belongsTo - add a foreign key to source
• hasMany - adds a foreign key to target, unless you also specifiy that target hasMany source, in which case a junction table is created with sourceId and targetId

Creating an association will add a foreign key constraint to the attributes. All associations use CASCADE on update and SET NULL on delete, except for n:m, which also uses CASCADE on delete.

When creating associations, you can provide an alias, via the as option. This is useful if the same model
is associated twice, or you want your association to be called something other than the name of the target model.
As an example, consider the case where users have many pictures, one of which is their profile picture. All pictures
have a userId, but in addition the user model also has a profilePictureId, to be able to easily load the user's profile
picture.

User.hasMany(Picture)
User.belongsTo(Picture, { as: 'ProfilePicture', constraints: false })

user.getPictures() // gets you all pictures
user.getProfilePicture() // gets you only the profile picture

User.findAll({
  where: ...,
  include: [
    { model: Picture }, // load all pictures
    { model: Picture, as: 'ProfilePicture' }, // load the profile picture. Notice that the spelling must be the exact same as the one in the association
  ]
})

To get full control over the foreign key column added by sequelize, you can use the foreignKey option. It can either be a string, that specifies the name, or and object type definition,
equivalent to those passed to sequelize.define.

User.hasMany(Picture, { foreignKey: 'uid' })

The foreign key column in Picture will now be called uid instead of the default userId.

User.hasMany(Picture, {
  foreignKey: {
    name: 'uid'
    allowNull: false
  }
})

This specifies that the uid column can not be null. In most cases this will already be covered by the foreign key costraints, which sequelize creates automatically,
but can be usefull in case where the foreign keys are disabled, e.g. due to circular references (see constraints: false below).

When fetching associated models, you can limit your query to only load some models. These queries are written in the same way as queries to find/findAll. To only get pictures in JPG, you can do:

user.getPictures({
  where: {
    format: 'jpg'
  }
})

There are several ways to update and add new assoications. Continuing with our example of users and pictures:

user.addPicture(p) // Add a single picture

user.addPictures([p1, p2]) // Associate user with these two pictures, but don't touch any current associations
user.setPictures([p1, p2]) // Associate user with ONLY these two picture, all other associations will be deleted

You don't have to pass in a complete object to the association functions, if your associated model has a single primary key:

user.addPicture(req.query.pid) // Here pid is just an integer, representing the primary key of the picture

In the example above we have specified that a user belongs to his profile picture. Conceptually, this might not make sense,
but since we want to add the foreign key to the user model this is the way to do it.
Note how we also specified constraints: false for profile picture. This is because we add a foreign key from
user to picture (profilePictureId), and from picture to user (userId). If we were to add foreign keys to both, it would
create a cyclic dependency, and sequelize would not know which table to create first, since user depends on picture, and picture
depends on user. These kinds of problems are detected by sequelize before the models are synced to the database, and you will
get an error along the lines of Error: Cyclic dependency found. 'users' is dependent of itself. If you encounter this,
you should either disable some constraints, or rethink your associations completely.   // we can pass constraints: false to one of the associations to break up circular dependency. constraints: false causes sequelize not to generate foreign key ocntraint

hasOne(target, [options])

View code
Creates an association between this (the source) and the provided target. The foreign key is added on the target.

Example: User.hasOne(Profile). This will add userId to the profile table.

The following methods are injected on the source:

• get[AS] - for example getProfile(finder). The finder object is passed to target.find.
• set[AS] - for example setProfile(instance, options). Options are passed to target.save
• create[AS] - for example createProfile(value, options). Builds and saves a new instance of the associated model. Values and options are passed on to target.create

All methods return a promise

Params:

belongsTo(target, [options])

View code
Creates an association between this (the source) and the provided target. The foreign key is added on the source.

Example: Profile.belongsTo(User). This will add userId to the profile table.

The following methods are injected on the source:

• get[AS] - for example getUser(finder). The finder object is passed to target.find.
• set[AS] - for example setUser(instance, options). Options are passed to this.save
• create[AS] - for example createUser(value, options). Builds and saves a new instance of the associated model. Values and options are passed on to target.create

All methods return a promise

Params:

hasMany(target, [options])

View code
Create an association that is either 1:m or n:m.

// Create a 1:m association between user and project
User.hasMany(Project)

// Create a n:m association between user and project
User.hasMany(Project)
Project.hasMany(User)

By default, the name of the join table will be source+target, so in this case projectsusers. This can be overridden by providing either a string or a Model as through in the options.

The following methods are injected on the source:

• get[AS] - for example getPictures(finder). The finder object is passed to target.find.
• set[AS] - for example setPictures(instances, defaultAttributes|options). Update the associations. All currently associated models that are not in instances will be removed.
• add[AS] - for example addPicture(instance, defaultAttributes|options). Add another associated object.
• add[AS] [plural] - for example addPictures([instance1, instance2], defaultAttributes|options). Add some more associated objects.
• create[AS] - for example createPicture(values, options). Build and save a new association.
• remove[AS] - for example removePicture(instance). Remove a single association.
• remove[AS] [plural] - for example removePictures(instance). Remove multiple association.
• has[AS] - for example hasPicture(instance). Is source associated to this target?
• has[AS] [plural] - for example hasPictures(instances). Is source associated to all these targets?

All methods return a promise

If you use a through model with custom attributes, these attributes can be set when adding / setting new associations in two ways. Consider users and projects from before
with a join table that stores whether the project has been started yet:

var UserProjects = sequelize.define('userprojects', {
  started: Sequelize.BOOLEAN
})
User.hasMany(Project, { through: UserProjects })
Project.hasMany(User, { through: UserProjects })

jan.addProject(homework, { started: false }) // The homework project is not started yet
jan.setProjects([makedinner, doshopping], { started: true}) // Both shopping and dinner have been started

If you want to set several target instances, but with different attributes you have to set the attributes on the instance, using a property with the name of the through model:

p1.userprojects {
  started: true
}
user.setProjects([p1, p2], {started: false}) // The default value is false, but p1 overrides that.

Similarily, when fetching through a join table with custom attributes, these attributes will be available as an object with the name of the through model.

user.getProjects().success(function (projects) {
  var p1 = projects[0]
  p1.userprojects.started // Is this project started yet?
})

Params:

belongsToMany(target, [options])

View code
Create an N:M association with a join table

User.belongsToMany(Project)
Project.belongsToMany(User)

By default, the name of the join table will be source+target, so in this case projectsusers. This can be overridden by providing either a string or a Model as through in the options.

The following methods are injected on the source:

• get[AS] - for example getPictures(finder). The finder object is passed to target.find.
• set[AS] - for example setPictures(instances, defaultAttributes|options). Update the associations. All currently associated models that are not in instances will be removed.
• add[AS] - for example addPicture(instance, defaultAttributes|options). Add another associated object.
• add[AS] [plural] - for example addPictures([instance1, instance2], defaultAttributes|options). Add some more associated objects.
• create[AS] - for example createPicture(values, options). Build and save a new association.
• remove[AS] - for example removePicture(instance). Remove a single association.
• remove[AS] [plural] - for example removePictures(instance). Remove multiple association.
• has[AS] - for example hasPicture(instance). Is source associated to this target?
• has[AS] [plural] - for example hasPictures(instances). Is source associated to all these targets?

All methods return a promise

If you use a through model with custom attributes, these attributes can be set when adding / setting new associations in two ways. Consider users and projects from before
with a join table that stores whether the project has been started yet:

var UserProjects = sequelize.define('userprojects', {
  started: Sequelize.BOOLEAN
})
User.belongsToMany(Project, { through: UserProjects })
Project.belongsToMany(User, { through: UserProjects })

jan.addProject(homework, { started: false }) // The homework project is not started yet
jan.setProjects([makedinner, doshopping], { started: true}) // Both shopping and dinner has been started

If you want to set several target instances, but with different attributes you have to set the attributes on the instance, using a property with the name of the through model:

p1.userprojects {
  started: true
}
user.setProjects([p1, p2], {started: false}) // The default value is false, but p1 overrides that.

Similarily, when fetching through a join table with custom attributes, these attributes will be available as an object with the name of the through model.

user.getProjects().then(function (projects) {
  var p1 = projects[0]
  p1.userprojects.started // Is this project started yet?
})

Params:

This document is automatically generated based on source code comments. Please do not edit it directly, as your changes will be ignored. Please write on IRC, open an issue or a create a pull request if you feel something can be improved. For help on how to write source code documentation see JSDoc and dox