Hi There. I’m about to build a new API and I would...
# orm-helpd
DuckyDev
08/08/2022, 7:43 AMHi There. I’m about to build a new API and I would like to try Prisma this time.
However, the database already exists with 100+ tables in it. Is there a way to auto-generate the classes for the DB entities?
✅ 1
j
Jared Fraser
08/08/2022, 7:44 AMd
DuckyDev
08/08/2022, 7:46 AMThanks, I will take a look at that!
n
Nurul
08/08/2022, 9:43 AMWelcome to our community! 🙌
Do let us know in case you run into any issues in introspecting your database.
d
DuckyDev
08/08/2022, 10:10 AM@Nurul thanks, and I will 😄
DuckyDev
08/08/2022, 10:29 AM@Nurul so I rang
prisma db pullnestjs Copy code
import { INestApplication, Injectable, OnModuleInit } from '@nestjs/common';
import { PrismaClient } from '@prisma/client';
@Injectable()
export class DataService extends PrismaClient implements OnModuleInit {
async onModuleInit() {
await this.$connect();
}
async enableShutdownHooks(app: INestApplication) {
this.$on('beforeExit', async () => {
await app.close();
});
}
} Copy code
[Nest] 34568 - 08/08/2022, 12:27:54 ERROR [ExceptionHandler] @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.
In case this error is unexpected for you, please report it in <https://github.com/prisma/prisma/issues>
Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.DuckyDev
08/08/2022, 10:30 AMAm I still supposed to run
prisma generaten
Nurul
08/08/2022, 10:33 AMYes, you need to execute
prisma generated
DuckyDev
08/08/2022, 10:38 AMAaa I see. So Prisma generates a huge
schema Copy code
error: Field "Year" is already defined on model "tblibsclaims".
--> schema.prisma:704
|
703 | Year Int @default(0) @map("1Year")
704 | Year Int @default(0) @map("3Year")
|
error: Field "Years" is already defined on model "tblibsconvictions".
--> schema.prisma:718
|
717 | Years Int? @default(100) @map("3Years")
718 | Years Int? @default(100) @map("5Years")DuckyDev
08/08/2022, 10:41 AMAnd thanks for being so friendly!
🙌 1
n
Nurul
08/08/2022, 10:43 AMThat's correct, there can't be two fields with the same name.
d
DuckyDev
08/08/2022, 10:44 AMOooh, it is because the one who created the db named the fields 1Year, 3Year and so on…..
j
Jared Fraser
08/08/2022, 11:48 PMYou should be able to edit your schema and change the definition to suit.
example:
Copy code
703 | Year1 Int @default(0) @map("1Year")
704 | Year3 Int @default(0) @map("3Year")1Yeard
DuckyDev
08/12/2022, 7:31 AMI figured that out 🙂 thanks.
🙌 1
2 Views