Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

203
Vistas
Cannot query across one-to-many for property NestJS and TypeORM

I have two entities one is car and another one is carAvailability

import { Entity, Column, PrimaryGeneratedColumn, OneToMany } from 'typeorm';
import { CarAvailability } from 'src/car-availabilitys/car-availability.entity';

@Entity('cars')
export class Car {
  @PrimaryGeneratedColumn()
  id: number;

  @Column()
  name: string;

  @OneToMany(() => CarAvailability, (carAvailability) => carAvailability.car, {
    eager: true,
    cascade: true,
  })
  availabilities: CarAvailability[];
}

I am trying to add a service that queries and filters cars based on the availabilities. In My Service and tried two ways:

Method 1 with repo functions:

async test () {
  const startDateTime = '2012-04-24 02:25:43.511';

  return await this.repo.find({
    relations: ['availabilities'],
    where: {
      availabilities: {
        start_date_time: startDateTime
      }
    }
  });
}

Method 2 with query builder:

async test () {
  const startDateTime = '2012-04-24 02:25:43.511';

  return this.repo.createQueryBuilder('cars')
    .innerJoin('cars.availabilities', 'car_availabilities')
    .where("cars.availabilities.start_date_time = :startDateTime", { startDateTime })
    .getMany();
}

Method 1 error:

Error: Cannot query across one-to-many for property availabilities

Method 2 error:

QueryFailedError: missing FROM-clause entry for table "availabilities"

I feel like I am missing something but I am not sure. Have referred both NestJS and TypeORM docs but can't seem to figure out what went wrong.

about 4 years ago · Juan Pablo Isaza
3 Respuestas
Responde la pregunta

0

Using Method 2, because you aliased car.availabilities as car_availabilities, your where clause should use the alias name:

car_availabilities.start_date_time

not:

cars.availabilities.start_date_time
about 4 years ago · Juan Pablo Isaza Denunciar

0

Using Method 1 repo functions with nested query builder:

async test () {
  const startDateTime = '2012-04-24 02:25:43.511';

  return await this.repo.find({
    relations: ['availabilities'],
    where: (qb) => {
      qb.where('availabilities.start_date_time = :startDateTime', {
        startDateTime
      });
    }
  });
}
about 4 years ago · Juan Pablo Isaza Denunciar

0

Remove cascade from oneToMany side and put:

{
  cascade: true,
  onDelete: 'CASCADE',
  onUpdate:'CASCADE'
}

on manyToOne side.

And if you going to use relations: ['availabilities'] you can remove eager: true.

about 4 years ago · Juan Pablo Isaza Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda