typeorm/docs/transactions.md

Transactions

• Creating and using transactions
• Transaction decorators
• Using QueryRunner to create and control state of single database connection

Creating and using transactions

Transactions are creating using Connection or EntityManager. Examples:

import {getConnection} from "typeorm";

await getConnection().transaction(transactionalEntityManager => {
    
});

or

import {getManager} from "typeorm";

await getManager().transaction(transactionalEntityManager => {
    
});

Everything you want to run in a transaction must be executed in a callback:

import {getManager} from "typeorm";

await getManager().transaction(async transactionalEntityManager => {
    await transactionalEntityManager.save(users);
    await transactionalEntityManager.save(photos);
    // ...
});

The most important restriction when working in an transaction is, to ALWAYS use the provided instance of entity manager - transactionalEntityManager in this example. If you'll use global manager (from getManager or manager from connection) you'll have problems. You also cannot use classes which use global manager or connection to execute their queries. All operations MUST be executed using the provided transactional entity manager.

Transaction decorators

There are a few decorators which can help you organize your transactions - @Transaction, @TransactionManager and @TransactionRepository.

@Transaction wraps all its execution into a single database transaction, and @TransactionManager provides a transaction entity manager which must be used to execute queries inside this transaction:

@Transaction()
save(@TransactionManager() manager: EntityManager, user: User) {
    return manager.save(user);
}

You must always use the manager provided by @TransactionManager.

However, you can also inject transaction repository (which uses transaction entity manager under the hood), using @TransactionRepository:

@Transaction()
save(user: User, @TransactionRepository(User) userRepository: Repository<User>) {
    return userRepository.save(user);    
}

You can inject both built-in TypeORM's repositories like Repository, TreeRepository and MongoRepository (using @TransactionRepository(Entity) entityRepository: Repository<Entity>) or custom repositories (classes extending the built-in TypeORM's repositories classes and decorated with @EntityRepository) using the @TransactionRepository() customRepository: CustomRepository.

Using QueryRunner to create and control state of single database connection

QueryRunner provides a single database connection. Transactions are organized using query runners. Single transaction can be established only on a single query runner. You can manally create a query runner instance and control transaction state manually using it. Example:

import {getConnection} from "typeorm";

// get a connection and create a new query runner
const connection = getConnection();
const queryRunner = connection.createQueryRunner();

// establish real database connection using our new query runner
await queryRunner.connect();

// now we can execute any queries on a query runner, for example:
await queryRunner.query("SELECT * FROM users");

// we can also access entity manager that works with connection created by a query runner:
const users = await queryRunner.manager.find(User);

// lets now open a new transaction:
await queryRunner.startTransaction();

try {
    
    // execute some operations on this transaction:
    await queryRunner.manager.save(user1);
    await queryRunner.manager.save(user2);
    await queryRunner.manager.save(photos);
    
    // commit transaction now:
    await queryRunner.commitTransaction();
    
} catch (err) {
    
    // since we have errors lets rollback changes we made
    await queryRunner.rollbackTransaction();
    
}

There are 3 methods to control transactions in QueryRunner:

• startTransaction - starts a new transaction inside the query runner instance
• commitTransaction - commits all changes made using the query runner instance
• rollbackTransaction - rolls all changes made using the query runner instance back

Learn more about Query Runner.