Definition

Scoping allows you to define commonly used queries that you can easily use later. Scopes can include all the same attributes as regular finders, where, include, limit etc.

Scopes are defined in the model definition and can be finder objects, or functions returning finder objects - except for the default scope, which can only be an object:

  1. var Project = sequelize.define('project', {
  2.   // Attributes
  3. }, {
  4.   defaultScope: {
  5.     where: {
  6.       active: true
  7.     }
  8.   },
  9.   scopes: {
  10.     deleted: {
  11.       where: {
  12.         deleted: true
  13.       }
  14.     },
  15.     activeUsers: {
  16.       include: [
  17.         { model: User, where: { active: true }}
  18.       ]
  19.     }
  20.     random: function () {
  21.       return {
  22.         where: {
  23.           someNumber: Math.random()
  24.         }
  25.       }
  26.     },
  27.     accessLevel: function (value) {
  28.       return {
  29.         where: {
  30.           accessLevel: {
  31.             $gte: value
  32.           }
  33.         }
  34.       }
  35.     }
  36.   }
  37. });

You can also add scopes after a model has been defined by calling addScope. This is especially useful for scopes with includes, where the model in the include might not be defined at the time the other model is being defined.

The default scope is always applied. This means, that with the model definition above, Project.findAll() will create the following query:

  1. SELECT * FROM projects WHERE active = true

The default scope can be removed by calling .unscoped(), .scope(null), or by invoking another scope:

  1. Project.scope('deleted').findAll(); // Removes the default scope
  1. SELECT * FROM projects WHERE deleted = true

Usage

Scopes are applied by calling .scope on the model definition, passing the name of one or more scopes. .scope returns a fully functional model instance with all the regular methods: .findAll, .update, .count, .destroy etc. You can save this model instance and reuse it later:

  1. var DeletedProjects = Project.scope('deleted');
  3. DeletedProjects.findAll();
  4. // some time passes
  6. // let's look for deleted projects again!
  7. DeletedProjects.findAll();

Scopes apply to .find, .findAll, .count, .update and .destroy.

Scopes which are functions can be invoked in two ways. If the scope does not take any arguments it can be invoked as normally. If the scope takes arguments, pass an object:

  1. Project.scope('random', { method: ['accessLevel', 19]}).findAll();
  1. SELECT * FROM projects WHERE someNumber = 42 AND accessLevel >= 19

Merging

Several scopes can be applied simultaneously by passing an array of scopes to .scope, or by passing the scopes as consecutive arguments.

  1. // These two are equivalent
  2. Project.scope('deleted', 'activeUsers').findAll();
  3. Project.scope(['deleted', 'activeUsers']).findAll();
  1. SELECT * FROM projects
  2. INNER JOIN users ON projects.userId = users.id
  3. AND users.active = true

If you want to apply another scope alongside the default scope, pass the key defaultScope to .scope:

  1. Project.scope('defaultScope', 'deleted').findAll();
  1. SELECT * FROM projects WHERE active = true AND deleted = true

When invoking several scopes, keys from subsequent scopes will overwrite previous ones (similar to _.assign). Consider two scopes:

  1. {
  2.   scope1: {
  3.     where: {
  4.       firstName: 'bob',
  5.       age: {
  6.         $gt: 20
  7.       }
  8.     },
  9.     limit: 2
  10.   },
  11.   scope2: {
  12.     where: {
  13.       age: {
  14.         $gt: 30
  15.       }
  16.     },
  17.     limit: 10
  18.   }
  19. }

Calling .scope('scope1', 'scope2') will yield the following query

  1. WHERE firstName = 'bob' AND age > 30 LIMIT 10

Note how limit and age are overwritten by scope2, while firstName is preserved. limit, offset, order, paranoid, lock and raw are overwritten, while where and include are shallowly merged. This means that identical keys in the where objects, and subsequent includes of the same model will both overwrite each other.

The same merge logic applies when passing a find object directly to findAll on a scoped model:

  1. Project.scope('deleted').findAll({
  2.   where: {
  3.     firstName: 'john'
  4.   }
  5. })
  1. WHERE deleted = true AND firstName = 'john'

Here the deleted scope is merged with the finder. If we were to pass where: { firstName: 'john', deleted: false } to the finder, the deleted scope would be overwritten.

Associations

Sequelize has two different but related scope concepts in relation to associations. The difference is subtle but important:

  • Association scopes Allow you to specify default attributes when getting and setting associations - useful when implementing polymorphic associations. This scope is only invoked on the association between the two models, when using the get, set, add and create associated model functions
  • Scopes on associated models Allows you to apply default and other scopes when fetching associations, and allows you to pass a scoped model when creating associations. These scopes both apply to regular finds on the model and to find through the association.

As an example, consider the models Post and Comment. Comment is associated to several other models (Image, Video etc.) and the association between Comment and other models is polymorphic, which means that Comment stores a commentable column, in addition to the foreign key commentable_id.

The polymorphic association can be implemented with an association scope :

  1. this.Post.hasMany(this.Comment, {
  2.   foreignKey: 'commentable_id',
  3.   scope: {
  4.     commentable: 'post'
  5.   }
  6. });

When calling post.getComments(), this will automatically add WHERE commentable = 'post'. Similarly, when adding new comments to a post, commentable will automagically be set to 'post'. The association scope is meant to live in the background without the programmer having to worry about it - it cannot be disabled. For a more complete polymorphic example, see Association scopes

Consider then, that Post has a default scope which only shows active posts: where: { active: true }. This scope lives on the associated model (Post), and not on the association like the commentable scope did. Just like the default scope is applied when calling Post.findAll(), it is also applied when calling User.getPosts() - this will only return the active posts for that user.

To disable the default scope, pass scope: null to the getter: User.getPosts({ scope: null }). Similarly, if you want to apply other scopes, pass an array like you would to .scope:

  1. User.getPosts({ scope: ['scope1', 'scope2']});

If you want to create a shortcut method to a scope on an associated model, you can pass the scoped model to the association. Consider a shortcut to get all deleted posts for a user:

  1. var Post = sequelize.define('post', attributes, {
  2.   defaultScope: {
  3.     where: {
  4.       active: true
  5.     }
  6.   },
  7.   scopes: {
  8.     deleted: {
  9.       where: {
  10.         deleted: true
  11.       }
  12.     }
  13.   }
  14. });
  16. User.hasMany(Post); // regular getPosts association
  17. User.hasMany(Post.scope('deleted'), { as: 'deletedPosts' });
  1. User.getPosts(); // WHERE active = true
  2. User.getDeletedPosts(); // WHERE deleted = true