MichalLytek / MichalLytek/typegraphql-prisma
Schema.prisma file from hell
- Dominant language
- TypeScript
- Stars
- 918
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
I was wondering if somebody could do a quick ```npx prisma generate``` on my attached schema.prisma file. I've tried everything and I mean everything to get this to generate. Every time I get a core dump.
```
ubuntu@vultr:~/erp$ npx prisma db push
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "erp", schema "public" at "localhost:5432"
🚀 Your database is now in sync with your schema. Done in 1.00s
14: 0x102da6b [node]
15: 0xd5b2c9 v8::internal::Builtin_ArrayUnshift(int, unsigned long*, v8::internal::Isolate*) [node]
16: 0x15f2179 [node]
Aborted (core dumped)
✔ Generated Prisma Client (3.13.0 | library) to ./node_modules/@prisma/client in 7.33s
```
I've tried on Ubuntu 18.04 / 21.04 / 22.04. (all large instances with plenty of RAM-CPU) Various versions of node / prisma. I'm currently at a loss. There must be something in the file that Prisma doesn't like so I thought I would ask the experts.
Thanks in advance for any pointers on this. Cheers, Dave
[schema.prisma.tar.gz](https://github.com/MichalLytek/typegraphql-prisma/files/8617800/schema.prisma.tar.gz)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing `npx prisma generate` and `npx prisma db push` with the attached `schema.prisma` archive, noting the Prisma and Node.js versions used. Compare the generated output and core dump across the reported Ubuntu environments; done means the cause is identified and generation completes without the crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, postgresql, typescript
- Domain
- databases, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100