Repository

used to perform CRUD operations on an entityType

find

returns a result array based on the provided options

Arguments:

• options

  • limit - Determines the number of rows returned by the request, on the browser the default is 100 rows

  example:

  await this.remult.repo(Products).find({
   limit:10,
   page:2
  })

  • page - Determines the page number that will be used to extract the data

  example:

  await this.remult.repo(Products).find({
   limit:10,
   page:2
  })

  • load
  • include - An option used in the find and findFirst methods to specify which related entities should be included when querying the source entity. It allows you to eagerly load related data to avoid N+1 query problems.

  param:

  An object specifying the related entities to include, their options, and filtering criteria.

  Example usage:

  const orders = await customerRepo.find({
    include: {
      // Include the 'tags' relation for each customer.
      tags: true,
    },
  });

  In this example, the tags relation for each customer will be loaded and included in the query result.

  see:

  • Relations.toMany
  • Relations.toOne
  • RelationOptions
  • where - filters the data

  example:

  await taskRepo.find({where: { completed:false }})

  see:

  For more usage examples see EntityFilter

  • orderBy - Determines the order of items returned .

  example:

  await this.remult.repo(Products).find({ orderBy: { name: "asc" }})

  example:

  await this.remult.repo(Products).find({ orderBy: { price: "desc", name: "asc" }})

liveQuery

returns a result array based on the provided options

Arguments:

• options

  • limit - Determines the number of rows returned by the request, on the browser the default is 100 rows

  example:

  await this.remult.repo(Products).find({
   limit:10,
   page:2
  })

  • page - Determines the page number that will be used to extract the data

  example:

  await this.remult.repo(Products).find({
   limit:10,
   page:2
  })

  • load
  • include - An option used in the find and findFirst methods to specify which related entities should be included when querying the source entity. It allows you to eagerly load related data to avoid N+1 query problems.

  param:

  An object specifying the related entities to include, their options, and filtering criteria.

  Example usage:

  const orders = await customerRepo.find({
    include: {
      // Include the 'tags' relation for each customer.
      tags: true,
    },
  });

  In this example, the tags relation for each customer will be loaded and included in the query result.

  see:

  • Relations.toMany
  • Relations.toOne
  • RelationOptions
  • where - filters the data

  example:

  await taskRepo.find({where: { completed:false }})

  see:

  For more usage examples see EntityFilter

  • orderBy - Determines the order of items returned .

  example:

  await this.remult.repo(Products).find({ orderBy: { name: "asc" }})

  example:

  await this.remult.repo(Products).find({ orderBy: { price: "desc", name: "asc" }})

findFirst

returns the first item that matchers the where condition

example:

await taskRepo.findFirst({ completed:false })

example:

await taskRepo.findFirst({ completed:false },{ createIfNotFound: true })

Arguments:

• where - filters the data

see:

EntityFilter

• options

  • load
  • include - An option used in the find and findFirst methods to specify which related entities should be included when querying the source entity. It allows you to eagerly load related data to avoid N+1 query problems.

  param:

  An object specifying the related entities to include, their options, and filtering criteria.

  Example usage:

  const orders = await customerRepo.find({
    include: {
      // Include the 'tags' relation for each customer.
      tags: true,
    },
  });

  In this example, the tags relation for each customer will be loaded and included in the query result.

  see:

  • Relations.toMany
  • Relations.toOne
  • RelationOptions
  • where - filters the data

  example:

  await taskRepo.find({where: { completed:false }})

  see:

  For more usage examples see EntityFilter

  • orderBy - Determines the order of items returned .

  example:

  await this.remult.repo(Products).find({ orderBy: { name: "asc" }})

  example:

  await this.remult.repo(Products).find({ orderBy: { price: "desc", name: "asc" }})

  • useCache - determines if to cache the result, and return the results from cache.
  • createIfNotFound - If set to true and an item is not found, it's created and returned

findOne

returns the first item that matchers the where condition

example:

await taskRepo.findOne({ where:{ completed:false }})

example:

await taskRepo.findFirst({ where:{ completed:false }, createIfNotFound: true })

Arguments:

• options

  • load
  • include - An option used in the find and findFirst methods to specify which related entities should be included when querying the source entity. It allows you to eagerly load related data to avoid N+1 query problems.

  param:

  An object specifying the related entities to include, their options, and filtering criteria.

  Example usage:

  const orders = await customerRepo.find({
    include: {
      // Include the 'tags' relation for each customer.
      tags: true,
    },
  });

  In this example, the tags relation for each customer will be loaded and included in the query result.

  see:

  • Relations.toMany
  • Relations.toOne
  • RelationOptions
  • where - filters the data

  example:

  await taskRepo.find({where: { completed:false }})

  see:

  For more usage examples see EntityFilter

  • orderBy - Determines the order of items returned .

  example:

  await this.remult.repo(Products).find({ orderBy: { name: "asc" }})

  example:

  await this.remult.repo(Products).find({ orderBy: { price: "desc", name: "asc" }})

  • useCache - determines if to cache the result, and return the results from cache.
  • createIfNotFound - If set to true and an item is not found, it's created and returned

findId

returns the items that matches the id. If id is undefined | null, returns null

Arguments:

• id

• options

  • load
  • include - An option used in the find and findFirst methods to specify which related entities should be included when querying the source entity. It allows you to eagerly load related data to avoid N+1 query problems.

  param:

  An object specifying the related entities to include, their options, and filtering criteria.

  Example usage:

  const orders = await customerRepo.find({
    include: {
      // Include the 'tags' relation for each customer.
      tags: true,
    },
  });

  In this example, the tags relation for each customer will be loaded and included in the query result.

  see:

  • Relations.toMany
  • Relations.toOne
  • RelationOptions
  • useCache - determines if to cache the result, and return the results from cache.
  • createIfNotFound - If set to true and an item is not found, it's created and returned

groupBy

Performs an aggregation on the repository's entity type based on the specified options.

returns:

The result of the aggregation.

example:

// Grouping by country and city, summing the salary field, and ordering by country and sum of salary:
const results = await repo.groupBy({
  group: ['country', 'city'],
  sum: ['salary'],
  where: {
    salary: { $ne: 1000 },
  },
  orderBy: {
    country: 'asc',
    salary: {
      sum: 'desc',
    },
  },
});

// Accessing the results:
console.log(results[0].country); // 'uk'
console.log(results[0].city); // 'London'
console.log(results[0].$count); // count for London, UK
console.log(results[0].salary.sum); // Sum of salaries for London, UK

Arguments:

• options - The options for the aggregation.

  • group - Fields to group by. The result will include one entry per unique combination of these fields.
  • sum - Fields to sum. The result will include the sum of these fields for each group.
  • avg - Fields to average. The result will include the average of these fields for each group.
  • min - Fields to find the minimum value. The result will include the minimum value of these fields for each group.
  • max - Fields to find the maximum value. The result will include the maximum value of these fields for each group.
  • distinctCount - Fields to count distinct values. The result will include the distinct count of these fields for each group.
  • where - Filters to apply to the query before aggregation.

  see:

  EntityFilter

  • orderBy - Fields and aggregates to order the results by. The result can be ordered by groupBy fields, sum fields, average fields, min fields, max fields, and distinctCount fields.

aggregate

Performs an aggregation on the repository's entity type based on the specified options.

returns:

The result of the aggregation.

example:

// Aggregating  (summing the salary field across all items):
const totalSalary = await repo.aggregate({
  sum: ['salary'],
});
console.log(totalSalary.salary.sum); // Outputs the total sum of salaries

Arguments:

• options - The options for the aggregation.

query

Fetches data from the repository in a way that is optimized for handling large sets of entity objects.

Unlike the find method, which returns an array, the query method returns an iterable QueryResult object. This allows for more efficient data handling, particularly in scenarios that involve paging through large amounts of data.

The method supports pagination and aggregation in a single request. When aggregation options are provided, the result will include both the items from the current page and the results of the requested aggregation.

The query method is designed for asynchronous iteration using the for await statement.

example:

// Basic usage with asynchronous iteration:
for await (const task of taskRepo.query()) {
  // Perform some operation on each task
}

example:

// Querying with pagination:
const query = taskRepo.query({
  where: { completed: false },
  pageSize: 100,
});

let paginator = await query.paginator();
console.log('Number of items on the current page:', paginator.items.length);
console.log('Total pages:', Math.ceil(paginator.aggregate.$count / 100));

if (paginator.hasNextPage) {
  paginator = await paginator.nextPage();
  console.log('Items on the next page:', paginator.items.length);
}

example:

// Querying with aggregation:
const query = await repo.query({
  where: { completed: false },
  pageSize: 50,
  aggregates: {
    sum: ['salary'],
    average: ['age'],
  }
});

let paginator = await query.paginator();
// Accessing paginated items
console.table(paginator.items);

// Accessing aggregation results
console.log('Total salary:', paginator.aggregates.salary.sum); // Sum of all salaries
console.log('Average age:', paginator.aggregates.age.average);  // Average age

Arguments:

• options

count

Returns a count of the items matching the criteria.

see:

EntityFilter

example:

await taskRepo.count({ completed:false })

Arguments:

• where - filters the data

see:

EntityFilter

validate

Validates an item

example:

const error = repo.validate(task);
if (error){
  alert(error.message);
  alert(error.modelState.title);//shows the specific error for the title field
}
// Can also be used to validate specific fields
const error = repo.validate(task,"title")

Arguments:

• item
• fields

save

saves an item or item[] to the data source. It assumes that if an id value exists, it's an existing row - otherwise it's a new row

example:

await taskRepo.save({...task, completed:true })

Arguments:

• item

insert

Insert an item or item[] to the data source

example:

await taskRepo.insert({title:"task a"})

example:

await taskRepo.insert([{title:"task a"}, {title:"task b", completed:true }])

Arguments:

• item

update

Updates an item, based on its id

example:

taskRepo.update(task.id,{...task,completed:true})

Arguments:

• id
• item

updateMany

Updates all items that match the where condition.

Arguments:

• options

  • where - filters the data

  see:

  EntityFilter

  • set

upsert

Inserts a new entity or updates an existing entity based on the specified criteria. If an entity matching the where condition is found, it will be updated with the provided set values. If no matching entity is found, a new entity will be created with the given data.

The upsert method ensures that a row exists based on the where condition: if no entity is found, a new one is created. It can handle both single and multiple upserts.

returns:

A promise that resolves with the inserted or updated entity, or an array of entities if multiple options were provided.

example:

// Upserting a single entity: updates 'task a' if it exists, otherwise creates it.
taskRepo.upsert({ where: { title: 'task a' }, set: { completed: true } });

example:

// Upserting a single entity without additional `set` values: ensures that a row with the title 'task a' exists.
taskRepo.upsert({ where: { title: 'task a' } });

example:

// Upserting multiple entities: ensures both 'task a' and 'task b' exist, updating their `completed` status if found.
taskRepo.upsert([
  { where: { title: 'task a' }, set: { completed: true } },
  { where: { title: 'task b' }, set: { completed: true } }
]);

Arguments:

• options - The options that define the where condition and the set values. Can be a single object or an array of objects.

delete

Deletes an Item

Arguments:

• id

deleteMany

Deletes all items that match the where condition.

Arguments:

• options

  • where - filters the data

  see:

  EntityFilter

create

Creates an instance of an item. It'll not be saved to the data source unless save or insert will be called.

It's useful to start or reset a form taking your entity default values into account.

Arguments:

• item

toJson

• toJson

Arguments:

• item

fromJson

Translates a json object to an item instance

Arguments:

• x
• isNew

getEntityRef

returns an entityRef for an item returned by create, find etc...

Arguments:

• item

fields

Provides information about the fields of the Repository's entity

example:

console.log(repo.fields.title.caption) // displays the caption of a specific field
console.log(repo.fields.title.options)// writes the options that were defined for this field

metadata

The metadata for the entity

See:

EntityMetadata

addEventListener

• addEventListener

Arguments:

• listener

relations

• relations

Arguments:

• item