A @Transactional method decorator for Sequelize inspired by Java Spring's @Transactional annotation.

Simple integration with NestJS.

• sequelize v4-6

# npm
npm install --save sequelize-transactional-decorator
# yarn
yarn add sequelize-transactional-decorator

Before establishing any connections using Sequelize, you need to enable Sequelize to use node CLS:

import { initSequelizeCLS } from 'sequelize-transactional-decorator';


initSequelizeCLS();

Import SequelizeTransactionalModule.register() into your root application module.

Example:

@Module({
  imports: [
    SequelizeModule.forRoot({
      ...
    }),
    SequelizeTransactionalModule.register(),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}

If you specified custom connection name in SequelizeModule, pass connectionName into options:

@Module({
  imports: [
    SequelizeModule.forRoot({
      ...
      name: 'my-connection-name',
    }),
    SequelizeTransactionalModule.register({ connectionName: 'my-connection-name' }),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}

Just call initSequelizeTransactional after establishing a connection:

const sequelize = new Sequelize({ ... })

initSequelizeTransactional(sequelize) // pass your Sequelize conection here

Use @Transactional annotation on your class methods.

Example:

@Injectable()
export class AppService {
  constructor(
    @InjectModel(Something)
    private readonly something: typeof Something,
    private readonly anotherService: AnotherService,
  ) {}

  @Transactional()
  async appMethod(): Promise<void> {
    await this.something.create({ message: 'hello' });
    await this.something.create({ message: 'world' });
    await this.anotherService.method(); // other service's method will use the same transaction
  }
}

@Transactional decorator accepts options object:

{
  isolationLevel?: string; // Isolation Level of transaction. Default value depends on your Sequelize config or the database you use
  propagation?: string; // Default value is REQUIRED. Allowed options are described below
}

• REQUIRED (default) - If exists, use current transaction, otherwise create a new one.
• SUPPORTS - If exists, use current transaction, otherwise execute without transaction.
• MANDATORY - If exists, use current transaction, otherwise throw an exception.
• NEVER - Execute without transaction. If an active transaction exists, throw an exception.
• NOT_SUPPORTED - Execute without transaction, suspend an active transaction if it exists.
• REQUIRES_NEW - Always execute in a separate transaction, suspend an active transaction if it exists.

• READ UNCOMMITTED
• READ COMMITTED
• REPEATABLE READ
• SERIALIZABLE

For more info refer to your database documentation.

If you want to remove transactional logic from your unit tests, you can mock @Transactional decorator.

Example in Jest:

jest.mock('sequelize-transactional-decorator', () => ({
  Transactional: () => () => ({}),
}));

You can test your code with @Transactional as usual, if you configure it in tests following the same steps described above.

NOTE: you will have to run your tests sequentially (which may be slower) rather than in parallel.
This is because only one simultaneous Sequelize connection is supported in order for decorator to work.
For example, in jest you will need to use --runInBand option.