Field excluded when running prisma query to supabase
The following code:
Produces the following in the terminal:
Even though my users table contains a password field (see photo) in my supabase and it is in sync with my schema.
Any thoughts on why the prisma query won't select password (or updated_at or created_at for that matter)?
![No description](https://cdn.answeroverflow.com/1247034408397963384/Screenshot_2024-06-02_at_8.46.06_PM.png)
3 Replies
Interestingly enough, when I drop the example column and then push, and then run this:
I get the following:
Which means it's still expecting the example field. Why could that be?
For more context, I have the following schema:
I opened a ticket on github: https://github.com/prisma/prisma/issues/24390
GitHub
Why can't I access password in user? (ORM) (Postgres-Supabase) · Is...
Bug description Using the following query: const user = await prisma.user.findFirst({ where: { email: email } }); console.log("user:", user); Produces the following in the terminal: user:...
Wow. Fixed: just had to close and open vs code