Hey all. Is it possible to tell Prisma that use re...
# orm-help
y
Hey all. Is it possible to tell Prisma that use relation but not actually create foreign keys in the database? It’s all good, but my db is getting bigger, and I don’t want to worry about foreign keys during the scaling phase. My thought, since I am declaring all the relation explicitly, so Prisma would figure it out without relying on the FKs. And I know the data consistency is my problem now. I haven’t tried dropping FKs manually, I’ll try that as well, but I just wanted to ask initially just if possible,
r
@Yilmaz Ugurlu 👋 I don’t think this is possible but I will let @Joël confirm.
y
Thank you so much. Just thought after this comment: https://github.com/github/gh-ost/issues/331#issuecomment-266027731
I had similar experiences in the past, and I thought it would be wise to think those in advance. But I really don’t want to loose fluent API functionalities, that’s the key part of having Prisma.
And I had to put many relation to many tables, that I know will cause a lot of sync and indexing issues later on.
r
I confirmed with the team and it’s currently not possible without foreign keys. Also foreign keys are fine as long as you’re not operating at a scale that GitHub does. I would suggest creating a feature request here with your use case so that we can look into this 🙂
👍 2