Interface BelongsToManyCountAssociationsMixinOptions<T>

The options for the countAssociations mixin of the belongsToMany association.

See

BelongsToManyCountAssociationsMixin

interface BelongsToManyCountAssociationsMixinOptions<T> {
    [COMPLETES_TRANSACTION]?: boolean;
    connection?: null | AbstractConnection;
    scope?: string | boolean;
    transaction?: null | Transaction;
    where?: WhereOptions<Attributes<T>>;
}

Type Parameters

Hierarchy (view full)

Properties

[COMPLETES_TRANSACTION]? connection? scope? transaction? where?

Properties

Private Optional [COMPLETES_TRANSACTION]

[COMPLETES_TRANSACTION]?: boolean

Indicates if the query completes the transaction Internal only

Optional connection

connection?: null | AbstractConnection

The connection on which this query must be run. Mutually exclusive with Transactionable.transaction.

Can be used to ensure that a query is run on the same connection as a previous query, which is useful when configuring session options.

Specifying this option takes precedence over CLS Transactions. If a transaction is running in the current AsyncLocalStorage context, it will be ignored in favor of the specified connection.

Optional scope

scope?: string | boolean

Apply a scope on the related model, or remove its default scope by passing false.

Optional transaction

transaction?: null | Transaction

The transaction in which this query must be run. Mutually exclusive with Transactionable.connection.

If the Sequelize disableClsTransactions option has not been set to true, and a transaction is running in the current AsyncLocalStorage context, that transaction will be used, unless null or another Transaction is manually specified here.

Optional where

where?: WhereOptions<Attributes<T>>

The WHERE clause. Can be many things from a hash of attributes to raw SQL.

Visit https://sequelize.org/docs/v7/core-concepts/model-querying-basics/ for more information.

Settings

Member Visibility

Theme

On This Page

[COMPLETES_TRANSACTION]connectionscopetransactionwhere