Closed frankcollins3 closed 1 year ago
problem is that psql isn't catching that it's deleted and thinks it's still in the database. same situation panned out creating login process. Delete a username and the constraint checker: shows that a username that was just removed from psql isn't unique even though there's no data in psql [7:15pm]
attempting to do: retrieve associative user data from postgres through prisma invocation
🚨 error: 🚨 unique constraint failed fkey_id_index [1:47pm]
proposed approach: already solved. chatGPT couldn't help this out.
chat accurately confirmed had to remove id from graphQL schema. first made the mistake of removing returned endpoints/fields "id" from everything but the Data { } typeDef
solution
solution: remove id from graphQL query & schema & clientside invoke but keep id endpoint within the prisma.create statement.