NestJS yana haɗa da bank ta bayanai ta tsabta ta hanyar ORMs — mafi yawan lokacin TypeORM (haɗin aiki na rasmi @nestjs/typeorm) da Prisma (ORM na zamani, wanda ake amfani da shi ta hanyar ƙididdiga na tsohuwa). Duka biyu sun dace da tsarin module/provider/DI na NestJS.
({
: [
.({
: ,
: process..,
: [],
: ,
}),
.([]),
],
})
{}
// 2. define an entity (maps to a table)
@Entity()
export class User {
@PrimaryGeneratedColumn() id: number;
@Column() name: string;
@Column({ unique: true }) email: string;
}
// 3. inject the repository into a service
@Injectable()
export class UsersService {
constructor(
@InjectRepository(User) private usersRepo: Repository<User>,
) {}
findAll() { return this.usersRepo.find(); }
findOne(id: number) { return this.usersRepo.findOneBy({ id }); }
create(data: Partial<User>) { return this.usersRepo.save(data); }
}
TypeORM yana amfani da ajiyoyi @Entity (ma'allaka zuwa tebuluwa) da Repositorys na allora don bubutuwa — dacewa da tsarin DI na NestJS ta tsarewa ta hanyar @InjectRepository.
// 1. a PrismaService wraps the Prisma client (and manages connection lifecycle)
@Injectable()
export class PrismaService extends PrismaClient implements OnModuleInit {
async onModuleInit() { await this.$connect(); } // connect on startup
}
// 2. inject it and use the type-safe client
@Injectable()
export class UsersService {
constructor(private prisma: PrismaService) {}
findAll() { return this.prisma.user.findMany(); }
findOne(id: number) { return this.prisma.user.findUnique({ where: { id } }); }
create(data) { return this.prisma.user.create({ data }); }
}
Prisma yana bayar da aljan ɗin da cikakke-amfani daga fayil ƙirƙira; kuna dora shi a cikin PrismaService na allora kuma kuna amfani da shi a cikin ayyukanku.
⚠️ NEVER use `synchronize: true` (TypeORM) in production — it auto-alters your schema
and can DROP data. Use MIGRATIONS (version-controlled schema changes) instead.
Prisma: prisma migrate dev/deploy manages schema changes via migration files.
TypeORM → repository/active-record patterns, decorators, mature, official Nest integration
Prisma → schema-first, excellent type safety, great DX, growing popularity
Haɗin bank ta bayanai yana da mahimmanci — kusan kowannen baje zuwa jiya ta bayanai, kuma fahimtar yaya ake haɗa bank ta bayanai da NestJS ta tsabtar hanya ita ce sanin aiki na asali.
Duka manyan ORMs biyu sun dace da gida na NestJS ta tsabta: TypeORM ta hanyar modul na rasmi @nestjs/typeorm (ƙarfafa haɗi, ƙayyadaddun ajiyoyi @Entity, ƙira Repositorys ta DI) da Prisma ta hanyar PrismaService na allora (wanda ya ba da kyakkyawan bangare na nau'i).
Sanin yaya ake ƙarfafa haɗi, ƙayyadaddun tsari, da ƙira filin shiga-bayanai a cikin ayyuka — ajiye lokar bank ta bayanai a cikin ayyuka, waje daga mai-damre — ita ce mahimmanci don gina ainihin tsarukan NestJS.
Cikakke, fahimtar ƙa'idodin zuuwan jiya da synchronize (kada koyaushe auto-sync ƙirƙira a waje, inda za a iya lalata bayanai, amma in sa'a haka yi amfani da zuuwan jiya na ƙarfau-ƙirƙira) jiya ce mahimmanci na amincewa ta waje.
Ita ce aiki na yau-yau, dole ne ka sani kunshe, saboda daimakawa na bayanai ita ce magajiya ga haɓaka baje, kuma haɗin ORM ita ce yadda tsarukan NestJS suka ajiye kuma suka dawo da bayanai nasu.