Restrict and ignore associated field in typeorm

Question

Restrict and ignore associated field in typeorm

I need help in restricting the related data when querying using query builder. Here is the code I have for fetching employee orders:

import { getRepository, Repository } from "typeorm";

public async findEmployeeQuery(id : number) {
    try {
        let query = await getRepository(Employees)
        .createQueryBuilder('employee')
        .where('employee.id = :id' , {id})
        .leftJoinAndSelect('employee.customers' , 'customers')
        .getOne()
        const user = query
        return user
    } catch (error) {
        throw error
    }

}

Now I want to control the number of customers returned for each request - is there a way to do that?

I experimented with the limit and skip options, but they only seem to work for the employee entity and not for the related data.

typescript nestjs typeorm

Answer 1

Answer №1

To narrow down the list of customers, you will need to run an additional query:

import { getRepository, Repository } from "typeorm";

public async fetchEmployeeInformation(id : number) {
    try {
        let employeeData = await getRepository(Employees)
        .createQueryBuilder('employee')
        .where('employee.id = :id' , {id})
        .getOne()

        employeeData.customers = await getRepository(Customers)
        .createQueryBuilder('customer')
        .where('customer.employee= :id' , {user.id})
        .limit(10) // specify the limit here
        .getMany()

        return employeeData;
    } catch (error) {
        throw error
    }
}

Answer 2

To narrow down the list of customers, you will need to run an additional query:

import { getRepository, Repository } from "typeorm";

public async fetchEmployeeInformation(id : number) {
    try {
        let employeeData = await getRepository(Employees)
        .createQueryBuilder('employee')
        .where('employee.id = :id' , {id})
        .getOne()

        employeeData.customers = await getRepository(Customers)
        .createQueryBuilder('customer')
        .where('customer.employee= :id' , {user.id})
        .limit(10) // specify the limit here
        .getMany()

        return employeeData;
    } catch (error) {
        throw error
    }
}

Answer 3

Answer №2

I have devised a neat solution for this issue...

This could be beneficial for others as TypeORM currently lacks support for pagination in relations (fingers crossed for future updates! =) )

 let category: any = await Category.findOne({
      where: {
        id: id,
      },
    });
    // searching for products associated with that category
    let products = await orm
      .createQueryBuilder("products", "p")
      .innerJoinAndSelect("p.categories", "c", "c.id = :categoryId", {
        categoryId: id,
      })
      // incorporating pagination
      .skip(offset)
      .take(limit)
      .getMany();
    // Connecting the array to the Category Object
    category.products = products;

Answer 4

I have devised a neat solution for this issue...

This could be beneficial for others as TypeORM currently lacks support for pagination in relations (fingers crossed for future updates! =) )

 let category: any = await Category.findOne({
      where: {
        id: id,
      },
    });
    // searching for products associated with that category
    let products = await orm
      .createQueryBuilder("products", "p")
      .innerJoinAndSelect("p.categories", "c", "c.id = :categoryId", {
        categoryId: id,
      })
      // incorporating pagination
      .skip(offset)
      .take(limit)
      .getMany();
    // Connecting the array to the Category Object
    category.products = products;

Answer 5

Answer №3

import { getRepository, Repository } from "typeorm";

public async retrieveEmployeeData(id : number) {
    try {
        let employeeData = await getRepository(Employees)
        .createQueryBuilder('employee')
        .where('employee.id = :id' , {id})
        .leftJoinAndSelect('employee.customers' , 'customers')
        .take(4) // limits to 4 records
        .skip(5) // offset by 5 entities
        .getOne()

        return employeeData
    } catch (error) {
        throw error
    }
}

Answer 6

import { getRepository, Repository } from "typeorm";

public async retrieveEmployeeData(id : number) {
    try {
        let employeeData = await getRepository(Employees)
        .createQueryBuilder('employee')
        .where('employee.id = :id' , {id})
        .leftJoinAndSelect('employee.customers' , 'customers')
        .take(4) // limits to 4 records
        .skip(5) // offset by 5 entities
        .getOne()

        return employeeData
    } catch (error) {
        throw error
    }
}

Restrict and ignore associated field in typeorm

Answer №1

Answer №2

Answer №3

Similar questions

Error: There was a problem trying to import the `.d.ts` file

Error importing Firestore in Firebase Cloud Function

The index declaration file has not been uploaded to NPM

Navigational menu routing with AngularJS2 using router link paths

The Sanity npm package encounters a type error during the build process

Encountering incorrect month while utilizing the new Date() object

Is TypeScript declaration merging not functioning properly?

NextJS API routes consistently provide a status code of 200 upon execution

What situations call for the use of 'import * as' in TypeScript?

Utilize array mapping to alter the complete object

The challenge of handling Set type in TypeScript errors

An issue has occurred: The module named 'ApprovalModule' must be compiled using the JIT compiler, however, the necessary compiler '@angular/compiler' is not currently accessible

What is the correct way to express an object in an array?

Problem with organizing data by dates

When it comes to passing prop values through functions, TypeScript types do not provide suggestions

Form an object using elements of a string array

Is it possible to utilize BE-provided Enum in the FE and if so, how can

Troubleshooting issue with React and Material UI Table pagination display

Troubleshooting Angular: Issues with Table Data Display and Source Map Error

What is the best way to use form input to filter an Observable?