Why Entity definition in NestJS? - Purpose & Use Cases

The Big Idea

What if you could stop worrying about SQL errors and focus on building features instead?

The Scenario

Imagine building a web app where you manually write SQL queries everywhere to handle user data, products, and orders.

You have to remember table structures, write long queries, and convert raw data into usable objects each time.

The Problem

Manually writing SQL and handling data mapping is slow and error-prone.

It's easy to make mistakes like typos in column names or forget to update queries when the database changes.

This leads to bugs and wasted time fixing them.

The Solution

Entity definition in NestJS lets you describe your data models as classes.

This creates a clear, reusable blueprint that automatically maps to database tables.

You write less code, avoid errors, and focus on your app's logic instead of database details.

Before vs After

✗ Before

const result = await db.query('SELECT * FROM users WHERE id = ?', [userId]);
const user = { id: result[0].id, name: result[0].name };

✓ After

import { Entity, PrimaryGeneratedColumn, Column } from 'typeorm';

@Entity()
class User {
  @PrimaryGeneratedColumn()
  id: number;

  @Column()
  name: string;
}

const user = await userRepository.findOneBy({ id: userId });

What It Enables

It enables you to work with data as simple objects in your code, making database operations safer and faster.

Real Life Example

When building an online store, you define entities like Product and Order once.

Then you can easily create, read, update, or delete products without writing raw SQL every time.

Key Takeaways

Manual SQL is repetitive and error-prone.

Entity definitions create clear data models as classes.

This simplifies database work and reduces bugs.