Table "appointment" does not exist in the current database error, but other routes do alright
Hi. I'm using T3 with App Router and I am running into an issue with tRPC and Prisma.
I have an
How can I fix this?
appointment tRPC router that handles and returns data from Prisma. I have a page where all appointments are rendered within a table - everything fetches just fine. But when I want to perform a mutation of one appointment, tRPC spits out a Prisma error saying that the appointment table doesn't exist.
There are no steps to reproduce, unless it has something to do with creating a trigger manually through the command line in PSQL.How can I fix this?
Solution:Jump to solution
Ugh, I love trying for hours to no avail, posting a question and solving it within 10 minutes. It was the trigger returning an error every interaction because I misspelled a relation.
1 Reply
Solution
Ugh, I love trying for hours to no avail, posting a question and solving it within 10 minutes. It was the trigger returning an error every interaction because I misspelled a relation.