TypeORM module setup in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the TypeORM module in a NestJS module.

NestJS

import { Module } from '@nestjs/common';
import { TypeOrmModule } from '[1]';

@Module({
  imports: [TypeOrmModule.forRoot()],
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

A@nestjs/typeorm

Btypeorm

C@nestjs/common

Dtypeorm-nestjs

Attempts:

3 left

💡 Hint

Common Mistakes

Importing from 'typeorm' directly instead of '@nestjs/typeorm'.

Using '@nestjs/common' for TypeORM import.

You import TypeOrmModule from @nestjs/typeorm to use TypeORM in NestJS.

2fill in blank

medium

Complete the code to configure the TypeORM connection with a PostgreSQL database.

NestJS

TypeOrmModule.forRoot({
  type: '[1]',
  host: 'localhost',
  port: 5432,
  username: 'user',
  password: 'pass',
  database: 'testdb',
  entities: [],
  synchronize: true,
})

Drag options to blanks, or click blank then click option'

Amysql

Bsqlite

Cpostgres

Dmariadb

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'mysql' or 'sqlite' instead of 'postgres'.

Misspelling the database type string.

The type property should be set to postgres for a PostgreSQL database.

3fill in blank

hard

Fix the error in the entities array to include the User entity correctly.

NestJS

import { User } from './user.entity';

TypeOrmModule.forRoot({
  type: 'postgres',
  host: 'localhost',
  port: 5432,
  username: 'user',
  password: 'pass',
  database: 'testdb',
  entities: [[1]],
  synchronize: true,
})

Drag options to blanks, or click blank then click option'

A'User'

BUser

Cuser

DUserEntity

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the entity name as a string.

Using a variable name that is not imported.

The entities array should contain the class reference User, not a string.

4fill in blank

hard

Fill both blanks to import and register the User entity in the feature module.

NestJS

import { Module } from '@nestjs/common';
import { TypeOrmModule } from '@nestjs/typeorm';
import { [1] } from './user.entity';

@Module({
  imports: [TypeOrmModule.forFeature([[2]])],
})
export class UserModule {}

Drag options to blanks, or click blank then click option'

AUser

BUserEntity

DUserModel

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for import and registration.

Using names not matching the entity class.

You import the User class and register it in forFeature using the same class name.

5fill in blank

hard

Fill all three blanks to inject the UserRepository and use it in the service constructor.

NestJS

import { Injectable } from '@nestjs/common';
import { InjectRepository } from '@nestjs/typeorm';
import { Repository } from 'typeorm';
import { [1] } from './user.entity';

@Injectable()
export class UserService {
  constructor(
    @InjectRepository([2])
    private readonly [3]: Repository<User>,
  ) {}
}

Drag options to blanks, or click blank then click option'

AUser

CuserRepository

DUserRepo

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for import and injection.

Naming the repository variable with uppercase or inconsistent style.

You import the User entity, inject its repository with @InjectRepository(User), and name the repository variable userRepository.

Practice

1. What is the main purpose of using TypeOrmModule.forRoot() in a NestJS application?

easy

A. To handle user authentication

B. To configure the database connection and entities for TypeORM

C. To create REST API endpoints automatically

D. To manage application state globally

Solution

1. Step 1: Understand the role of TypeOrmModule.forRoot()

   This method sets up the database connection and registers entities for TypeORM in NestJS.

2. Step 2: Identify what it does not do

   It does not create REST endpoints, handle authentication, or manage global state.

3. Final Answer:

   To configure the database connection and entities for TypeORM -> Option B

4. Quick Check:

   TypeOrmModule.forRoot() = Database setup [OK]

Hint: Remember: forRoot sets up DB connection and entities [OK]

Common Mistakes:

• Thinking it creates API routes
• Confusing it with authentication modules
• Assuming it manages app state

2. Which of the following is the correct way to import and configure TypeORM for PostgreSQL in a NestJS module?

easy

A. import { TypeOrmModule } from '@nestjs/typeorm';

@Module({
imports: [TypeOrmModule.forRoot({
type: 'sqlite',
database: ':memory:',
entities: [User],
synchronize: false,
})],
})

B. import { TypeOrmModule } from '@nestjs/typeorm';

@Module({
imports: [TypeOrmModule.forFeature({
type: 'postgres',
host: 'localhost',
port: 5432,
username: 'user',
password: 'pass',
database: 'testdb',
entities: [User],
synchronize: true,
})],
})

C. import { TypeOrmModule } from '@nestjs/typeorm';

@Module({
imports: [TypeOrmModule.forRootAsync({
useFactory: () => ({
type: 'mysql',
host: 'localhost',
port: 3306,
username: 'user',
password: 'pass',
database: 'testdb',
entities: [User],
synchronize: true,
}),
})],
})

D. import { TypeOrmModule } from '@nestjs/typeorm';

@Module({
imports: [TypeOrmModule.forRoot({
type: 'postgres',
host: 'localhost',
port: 5432,
username: 'user',
password: 'pass',
database: 'testdb',
entities: [User],
synchronize: true,
})],
})

Solution

1. Step 1: Identify the correct method for root configuration

   TypeOrmModule.forRoot() is used to configure the main database connection with options like type, host, port, entities, and synchronize.

2. Step 2: Check the options and syntax

   import { TypeOrmModule } from '@nestjs/typeorm'; @Module({ imports: [TypeOrmModule.forRoot({ type: 'postgres', host: 'localhost', port: 5432, username: 'user', password: 'pass', database: 'testdb', entities: [User], synchronize: true, })], }) correctly uses forRoot with proper PostgreSQL database config and entities array. import { TypeOrmModule } from '@nestjs/typeorm'; @Module({ imports: [TypeOrmModule.forFeature({ type: 'postgres', host: 'localhost', port: 5432, username: 'user', password: 'pass', database: 'testdb', entities: [User], synchronize: true, })], }) incorrectly uses forFeature for root config. import { TypeOrmModule } from '@nestjs/typeorm'; @Module({ imports: [TypeOrmModule.forRootAsync({ useFactory: () => ({ type: 'mysql', host: 'localhost', port: 3306, username: 'user', password: 'pass', database: 'testdb', entities: [User], synchronize: true, }), })], }) uses forRootAsync with MySQL config instead of PostgreSQL. import { TypeOrmModule } from '@nestjs/typeorm'; @Module({ imports: [TypeOrmModule.forRoot({ type: 'sqlite', database: ':memory:', entities: [User], synchronize: false, })], }) uses SQLite config instead of PostgreSQL.

3. Final Answer:

   The PostgreSQL configuration using TypeOrmModule.forRoot() -> Option D

4. Quick Check:

   forRoot() = main DB config [OK]

Hint: Use forRoot() for main DB setup, forFeature() for repositories [OK]

Common Mistakes:

• Using forFeature() instead of forRoot() for DB config
• Confusing forRootAsync with forRoot without async needs
• Setting synchronize false during development

3. Given this TypeORM configuration snippet in a NestJS app:

TypeOrmModule.forRoot({
  type: 'sqlite',
  database: ':memory:',
  entities: [User],
  synchronize: true,
})

What will happen when the app starts?

medium

A. An in-memory SQLite database is created, tables for User entity are auto-created

B. A persistent SQLite file database is created on disk

C. The app throws an error because ':memory:' is invalid

D. The User entity tables are not created automatically

Solution

1. Step 1: Understand ':memory:' in SQLite config

   Using ':memory:' creates a temporary in-memory database that exists only while the app runs.

2. Step 2: Effect of synchronize: true

   With synchronize: true, TypeORM automatically creates tables for all entities (like User) on app start.

3. Final Answer:

   An in-memory SQLite database is created, tables for User entity are auto-created -> Option A

4. Quick Check:

   ':memory:' + synchronize: true = auto in-memory tables [OK]

Hint: ':memory:' means temporary DB; synchronize true creates tables [OK]

Common Mistakes:

• Thinking ':memory:' creates a file on disk
• Assuming tables need manual creation
• Believing ':memory:' is invalid syntax

4. You wrote this TypeORM setup in your NestJS app:

TypeOrmModule.forRoot({
  type: 'postgres',
  host: 'localhost',
  port: 5432,
  username: 'user',
  password: 'pass',
  database: 'testdb',
  entities: [User],
  synchronize: true
})

But the app crashes with an error: "Entity metadata not found for User". What is the likely cause?

medium

A. The User entity class is not imported or registered correctly in entities array

B. The database connection details are incorrect

C. synchronize: true is not allowed with Postgres

D. TypeOrmModule.forRoot() must be called inside a service, not a module

Solution

1. Step 1: Analyze the error message

   "Entity metadata not found for User" means TypeORM cannot find the User entity definition.

2. Step 2: Check entities registration

   This usually happens if the User entity class is not imported or not included properly in the entities array of the config.

3. Final Answer:

   The User entity class is not imported or registered correctly in entities array -> Option A

4. Quick Check:

   Missing entity import = metadata error [OK]

Hint: Always import and add entities to entities array [OK]

Common Mistakes:

• Forgetting to import entity classes
• Misplacing entities array outside forRoot config
• Assuming synchronize causes this error

5. You want to set up TypeORM in a NestJS app to connect to a MySQL database, but only synchronize the schema during development, not in production. Which setup correctly achieves this?

hard

A. TypeOrmModule.forRoot({
type: 'mysql',
host: 'localhost',
port: 3306,
username: 'root',
password: 'pass',
database: 'appdb',
entities: [User],
synchronize: false,
})

B. TypeOrmModule.forRoot({
type: 'mysql',
host: 'localhost',
port: 3306,
username: 'root',
password: 'pass',
database: 'appdb',
entities: [User],
synchronize: true,
})

C. TypeOrmModule.forRoot({
type: 'mysql',
host: 'localhost',
port: 3306,
username: 'root',
password: 'pass',
database: 'appdb',
entities: [User],
synchronize: process.env.NODE_ENV === 'development',
})

D. TypeOrmModule.forRootAsync({
useFactory: () => ({
type: 'mysql',
host: 'localhost',
port: 3306,
username: 'root',
password: 'pass',
database: 'appdb',
entities: [User],
synchronize: false,
}),
})

Solution

1. Step 1: Understand conditional synchronize setting

   To synchronize only in development, synchronize should be true only when NODE_ENV is 'development'.

2. Step 2: Check options for conditional synchronize

   TypeOrmModule.forRoot({ type: 'mysql', host: 'localhost', port: 3306, username: 'root', password: 'pass', database: 'appdb', entities: [User], synchronize: process.env.NODE_ENV === 'development', }) uses synchronize: process.env.NODE_ENV === 'development', which correctly sets synchronize true only in development.

3. Step 3: Review other options

   TypeOrmModule.forRoot({ type: 'mysql', host: 'localhost', port: 3306, username: 'root', password: 'pass', database: 'appdb', entities: [User], synchronize: true, }) always synchronizes (bad for production). TypeOrmModule.forRoot({ type: 'mysql', host: 'localhost', port: 3306, username: 'root', password: 'pass', database: 'appdb', entities: [User], synchronize: false, }) never synchronizes (bad for development). TypeOrmModule.forRootAsync({ useFactory: () => ({ type: 'mysql', host: 'localhost', port: 3306, username: 'root', password: 'pass', database: 'appdb', entities: [User], synchronize: false, }), }) uses forRootAsync but sets synchronize false always, so no conditional sync.

4. Final Answer:

   synchronize: process.env.NODE_ENV === 'development' -> Option C

5. Quick Check:

   Conditional synchronize = process.env.NODE_ENV check [OK]

Hint: Use environment variable to toggle synchronize true/false [OK]

Common Mistakes:

• Always setting synchronize true in production
• Never enabling synchronize during development
• Not using environment variables for config