Repository APIs

Repository API

  • manager - The EntityManager used by this repository.
  1. const manager = repository.manager;
  1. const metadata = repository.metadata;
  • queryRunner - The query runner used by EntityManager.Used only in transactional instances of EntityManager.
  1. const queryRunner = repository.queryRunner;
  • target - The target entity class managed by this repository.Used only in transactional instances of EntityManager.
  1. const target = repository.target;
  • createQueryBuilder - Creates a query builder use to build SQL queries.Learn more about QueryBuilder.
  1. const users = await repository
  2.     .createQueryBuilder("user")
  3.     .where("user.name = :name", { name: "John" })
  4.     .getMany();
  • hasId - Checks if the given entity’s primary column property is defined.
  1.  if (repository.hasId(user)) {
  2.     // ... do something
  3.  }
  • getId - Gets the primary column property values of the given entity.If entity has composite primary keys then the returned value will be an object with names and values of primary columns.
  1. const userId = repository.getId(user); // userId === 1
  • create - Creates a new instance of User. Optionally accepts an object literal with user propertieswhich will be written into newly created user object
  1. const user = repository.create(); // same as const user = new User();
  2. const user = repository.create({
  3.     id: 1,
  4.     firstName: "Timber",
  5.     lastName: "Saw"
  6. }); // same as const user = new User(); user.firstName = "Timber"; user.lastName = "Saw";
  • merge - Merges multiple entities into a single entity.
  1. const user = new User();
  2. repository.merge(user, { firstName: "Timber" }, { lastName: "Saw" }); // same as user.firstName = "Timber"; user.lastName = "Saw";
  • preload - Creates a new entity from the given plain javascript object. If the entity already exists in the database, thenit loads it (and everything related to it), replaces all values with the new ones from the given object,and returns the new entity. The new entity is actually an entity loaded from the database with all propertiesreplaced from the new object.
  1. const partialUser = {
  2.     id: 1,
  3.     firstName: "Rizzrak",
  4.     profile: {
  5.         id: 1
  6.     }
  7. };
  8. const user = await repository.preload(partialUser);
  9. // user will contain all missing data from partialUser with partialUser property values:
  10. // { id: 1, firstName: "Rizzrak", lastName: "Saw", profile: { id: 1, ... } }
  • save - Saves a given entity or array of entities.If the entity already exist in the database, it is updated.If the entity does not exist in the database, it is inserted.It saves all given entities in a single transaction (in the case of entity, manager is not transactional).Also supports partial updating since all undefined properties are skipped.Returns the saved entity/entities.
  1. await repository.save(user);
  2. await repository.save([
  3.     category1,
  4.     category2,
  5.     category3
  6. ]);
  • remove - Removes a given entity or array of entities.It removes all given entities in a single transaction (in the case of entity, manager is not transactional).Returns the removed entity/entities.
  1. await repository.remove(user);
  2. await repository.remove([
  3.     category1,
  4.     category2,
  5.     category3
  6. ]);
  • insert - Inserts a new entity, or array of entities.
  1. await repository.insert({
  2.     firstName: "Timber",
  3.     lastName: "Timber"
  4. });
  7. await manager.insert(User, [{ 
  8.     firstName: "Foo", 
  9.     lastName: "Bar" 
  10. }, { 
  11.     firstName: "Rizz", 
  12.     lastName: "Rak" 
  13. }]);
  • update - Partially updates entity by a given update options or entity id.
  1. await repository.update({ firstName: "Timber" }, { firstName: "Rizzrak" });
  2. // executes UPDATE user SET firstName = Rizzrak WHERE firstName = Timber
  4. await repository.update(1, { firstName: "Rizzrak" });
  5. // executes UPDATE user SET firstName = Rizzrak WHERE id = 1
  • delete - Deletes entities by entity id, ids or given conditions:
  1. await repository.delete(1);
  2. await repository.delete([1, 2, 3]);
  3. await repository.delete({ firstName: "Timber" });
  • count - Counts entities that match given options. Useful for pagination.
  1. const count = await repository.count({ firstName: "Timber" });
  • increment - Increments some column by provided value of entities that match given options.
  1. await manager.increment(User, { firstName: "Timber" }, "age", 3);

  • decrement - Decrements some column by provided value that match given options.

    1. await manager.decrement(User, { firstName: "Timber" }, "age", 3);

  • find - Finds entities that match given options.

  1. const timbers = await repository.find({ firstName: "Timber" });
  • findAndCount - Finds entities that match given find options.Also counts all entities that match given conditions,but ignores pagination settings (skip and take options).
  1. const [timbers, timbersCount] = await repository.findAndCount({ firstName: "Timber" });
  • findByIds - Finds multiple entities by id.
  1. const users = await repository.findByIds([1, 2, 3]);
  • findOne - Finds first entity that matches some id or find options.
  1. const user = await repository.findOne(1);
  2. const timber = await repository.findOne({ firstName: "Timber" });
  • findOneOrFail - Finds the first entity that matches the some id or find options.Rejects the returned promise if nothing matches.
  1. const user = await repository.findOneOrFail(1);
  2. const timber = await repository.findOneOrFail({ firstName: "Timber" });
  • query - Executes a raw SQL query.
  1. const rawData = await repository.query(`SELECT * FROM USERS`);
  • clear - Clears all the data from the given table (truncates/drops it).
  1. await repository.clear();

Additional Options

Optional SaveOptions can be passed as parameter for save, insert and update.

  • data - Additional data to be passed with persist method. This data can be used in subscribers then.
  • listeners: boolean - Indicates if listeners and subscribers are called for this operation. By default they are enabled, you can disable them by setting { listeners: false } in save/remove options.
  • transaction: boolean - By default transactions are enabled and all queries in persistence operation are wrapped into the transaction. You can disable this behaviour by setting { transaction: false } in the persistence options.
  • chunk: number - Breaks save execution into multiple groups of chunks. For example, if you want to save 100.000 objects but you have issues with saving them, you can break them into 10 groups of 10.000 objects (by setting { chunk: 10000 }) and save each group separately. This option is needed to perform very big insertions when you have issues with underlying driver parameter number limitation.
  • reload: boolean - Flag to determine whether the entity that is being persisted should be reloaded during the persistence operation. It will work only on databases which does not support RETURNING / OUTPUT statement. Enabled by default.

Example:

  1. // users contains array of User Entities
  2. userRepository.insert(users, {chunk: users.length / 1000});

Optional RemoveOptions can be passed as parameter for remove and delete.

  • data - Additional data to be passed with remove method. This data can be used in subscribers then.
  • listener: boolean - Indicates if listeners and subscribers are called for this operation. By default they are enabled, you can disable them by setting { listeners: false } in save/remove options.
  • transaction: boolean - By default transactions are enabled and all queries in persistence operation are wrapped into the transaction. You can disable this behaviour by setting { transaction: false } in the persistence options.
  • chunk: number - Breaks save execution into multiple groups of chunks. For example, if you want to save 100.000 objects but you have issues saving them, you can break them into 10 groups of 10.000 objects, by setting { chunk: 10000 }, and save each group separately. This option is needed to perform very big insertions when you have issues with underlying driver parameter number limitation.

Example:

  1. // users contains array of User Entities
  2. userRepository.remove(users, {chunk: entities.length / 1000});

TreeRepository API

For TreeRepository API refer to the Tree Entities documentation.

MongoRepository API

For MongoRepository API refer to the MongoDB documentation.