Skip to main content
Version: Next

EntityRepository <Entity>

Hierarchy

Index

Constructors

constructor

Methods

assign

  • Shortcut for wrap(entity).assign(data, { em })


    Type parameters

    • Ent: object | { [___loadedType]?: Entity } | { [___selectedType]?: [Entity, any, any] }
    • Naked: object | { [___loadedType]?: Entity } | { [___selectedType]?: [Entity, any, any] } = FromEntityType<Ent>
    • Data: EntityData<Naked> | Partial<EntityDTO<Naked>> = EntityData<Naked> | Partial<EntityDTO<Naked>>

    Parameters

    Returns MergeSelected<Ent, Naked, keyof Data & string>

canPopulate

  • canPopulate(property: string): boolean
  • Checks whether given property can be populated on the entity.


    Parameters

    • property: string

    Returns boolean

count

  • Returns total number of entities matching your where query.


    Type parameters

    • Hint: string = never

    Parameters

    Returns Promise<number>

create

  • Creates new instance of given entity and populates it with given data. The entity constructor will be used unless you provide { managed: true } in the options parameter. The constructor will be given parameters based on the defined constructor of the entity. If the constructor parameter matches a property name, its value will be extracted from data. If no matching property exists, the whole data parameter will be passed. This means we can also define constructor(data: Partial<Entity>) and em.create() will pass the data into it (unless we have a property named data too).


    Parameters

    Returns Entity

find

  • find<Hint, Fields, Excludes>(where: FilterQuery<Entity>, options?: FindOptions<Entity, Hint, Fields, Excludes>): Promise<Loaded<Entity, Hint, Fields, Excludes>[]>
  • Finds all entities matching your where query. You can pass additional options via the options parameter.


    Type parameters

    • Hint: string = never
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<Loaded<Entity, Hint, Fields, Excludes>[]>

findAll

  • findAll<Hint, Fields, Excludes>(options?: FindAllOptions<Entity, Hint, Fields, Excludes>): Promise<Loaded<Entity, Hint, Fields, Excludes>[]>
  • Finds all entities of given type. You can pass additional options via the options parameter.


    Type parameters

    • Hint: string = never
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<Loaded<Entity, Hint, Fields, Excludes>[]>

findAndCount

  • findAndCount<Hint, Fields, Excludes>(where: FilterQuery<Entity>, options?: FindOptions<Entity, Hint, Fields, Excludes>): Promise<[Loaded<Entity, Hint, Fields, Excludes>[], number]>
  • Calls em.find() and em.count() with the same arguments (where applicable) and returns the results as tuple where first element is the array of entities, and the second is the count.


    Type parameters

    • Hint: string = never
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<[Loaded<Entity, Hint, Fields, Excludes>[], number]>

findByCursor

  • Calls em.find() and em.count() with the same arguments (where applicable) and returns the results as Cursor object. Supports before, after, first and last options while disallowing limit and offset. Explicit orderBy option is required.

    Use first and after for forward pagination, or last and before for backward pagination.

    • first and last are numbers and serve as an alternative to offset, those options are mutually exclusive, use only one at a time
    • before and after specify the previous cursor value, it can be one of the:
      • Cursor instance
      • opaque string provided by startCursor/endCursor properties
      • POJO/entity instance
    const currentCursor = await em.findByCursor(User, {}, {
    first: 10,
    after: previousCursor, // cursor instance
    orderBy: { id: 'desc' },
    });

    // to fetch next page
    const nextCursor = await em.findByCursor(User, {}, {
    first: 10,
    after: currentCursor.endCursor, // opaque string
    orderBy: { id: 'desc' },
    });

    // to fetch next page
    const nextCursor2 = await em.findByCursor(User, {}, {
    first: 10,
    after: { id: lastSeenId }, // entity-like POJO
    orderBy: { id: 'desc' },
    });

    The Cursor object provides the following interface:

    Cursor<User> {
    items: [
    User { ... },
    User { ... },
    User { ... },
    ],
    totalCount: 50,
    startCursor: 'WzRd',
    endCursor: 'WzZd',
    hasPrevPage: true,
    hasNextPage: true,
    }

    Type parameters

    • Hint: string = never
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<Cursor<Entity, Hint, Fields, Excludes>>

findOne

  • findOne<Hint, Fields, Excludes>(where: FilterQuery<Entity>, options?: FindOneOptions<Entity, Hint, Fields, Excludes>): Promise<null | Loaded<Entity, Hint, Fields, Excludes>>
  • Finds first entity matching your where query.


    Type parameters

    • Hint: string = never
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<null | Loaded<Entity, Hint, Fields, Excludes>>

findOneOrFail

  • Finds first entity matching your where query. If nothing is found, it will throw an error. You can override the factory for creating this method via options.failHandler locally or via Configuration.findOneOrFailHandler globally.


    Type parameters

    • Hint: string = never
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<Loaded<Entity, Hint, Fields, Excludes>>

getEntityManager

getEntityName

  • getEntityName(): string
  • Returns string

getReference

  • Gets a reference to the entity identified by the given type and identifier without actually loading it, if the entity is not yet loaded


    Parameters

    Returns Ref<Entity>

insert

insertMany

map

  • Maps raw database result to an entity and merges it to this EntityManager.


    Parameters

    Returns Entity

merge

  • Merges given entity to this EntityManager so it becomes managed. You can force refreshing of existing entities via second parameter. By default it will return already loaded entities without modifying them.


    Parameters

    Returns Entity

nativeDelete

  • Fires native delete query. Calling this has no side effects on the context (identity map).


    Parameters

    Returns Promise<number>

nativeUpdate

  • Fires native update query. Calling this has no side effects on the context (identity map).


    Parameters

    Returns Promise<number>

populate

  • populate<Ent, Hint, Naked, Fields, Excludes>(entities: Ent, populate: false | AutoPath<Entity, Hint, *>[], options?: EntityLoaderOptions<Entity, Fields, Excludes>): Promise<Ent extends object[] ? MergeLoaded<ArrayElement<Ent>, Naked, Hint, Fields, Excludes>[] : MergeLoaded<Ent, Naked, Hint, Fields, Excludes>>
  • Loads specified relations in batch. This will execute one query for each relation, that will populate it on all the specified entities.


    Type parameters

    • Ent: object | Entity[]
    • Hint: string = never
    • Naked: object = FromEntityType<Entity>
    • Fields: string = *
    • Excludes: string = never

    Parameters

    Returns Promise<Ent extends object[] ? MergeLoaded<ArrayElement<Ent>, Naked, Hint, Fields, Excludes>[] : MergeLoaded<Ent, Naked, Hint, Fields, Excludes>>

upsert

  • Creates or updates the entity, based on whether it is already present in the database. This method performs an insert on conflict merge query ensuring the database is in sync, returning a managed entity instance. The method accepts either entityName together with the entity data, or just entity instance.

    // insert into "author" ("age", "email") values (33, 'foo@bar.com') on conflict ("email") do update set "age" = 41
    const author = await em.getRepository(Author).upsert({ email: 'foo@bar.com', age: 33 });

    The entity data needs to contain either the primary key, or any other unique property. Let's consider the following example, where Author.email is a unique property:

    // insert into "author" ("age", "email") values (33, 'foo@bar.com') on conflict ("email") do update set "age" = 41
    // select "id" from "author" where "email" = 'foo@bar.com'
    const author = await em.getRepository(Author).upsert({ email: 'foo@bar.com', age: 33 });

    Depending on the driver support, this will either use a returning query, or a separate select query, to fetch the primary key if it's missing from the data.

    If the entity is already present in current context, there won't be any queries - instead, the entity data will be assigned and an explicit flush will be required for those changes to be persisted.


    Parameters

    Returns Promise<Entity>

upsertMany

  • Creates or updates the entity, based on whether it is already present in the database. This method performs an insert on conflict merge query ensuring the database is in sync, returning a managed entity instance.

    // insert into "author" ("age", "email") values (33, 'foo@bar.com') on conflict ("email") do update set "age" = 41
    const authors = await em.getRepository(Author).upsertMany([{ email: 'foo@bar.com', age: 33 }, ...]);

    The entity data needs to contain either the primary key, or any other unique property. Let's consider the following example, where Author.email is a unique property:

    // insert into "author" ("age", "email") values (33, 'foo@bar.com'), (666, 'lol@lol.lol') on conflict ("email") do update set "age" = excluded."age"
    // select "id" from "author" where "email" = 'foo@bar.com'
    const author = await em.getRepository(Author).upsertMany([
    { email: 'foo@bar.com', age: 33 },
    { email: 'lol@lol.lol', age: 666 },
    ]);

    Depending on the driver support, this will either use a returning query, or a separate select query, to fetch the primary key if it's missing from the data.

    If the entity is already present in current context, there won't be any queries - instead, the entity data will be assigned and an explicit flush will be required for those changes to be persisted.


    Parameters

    Returns Promise<Entity[]>