The column new does not exist in the current database on prisma create

[kvnam]

Hello,

I'm a little stumped with this error. All I did was change the name of a column (in Supabase) and then run npx prisma db pull and npx prisma generate in my Node express backend. Now when I try to create an entry I get this error:

The column "new" does not exist in the current database on prisma create

There is no column by that name anywhere in the DB, and I logged to see that the input passed to create as data is also clean and contains no new property. I re-ran the prisma commands a few more times in case the prisma schema was corrupt somehow, but that did not help either.

Any idea what could be causing this?

     "code": P2022", 
      clientVersion: 3.12.0, 
      meta: { column:new }
    }
      data:null
    }
   }

Update: I tried deleting and re-adding the column, updating the schema for each instance, and it gave an error in both cases (column removed and column added back)

Any help would be greatly appreciated, thanks!

[alucardu]

Do you need to run the migration?

[kvnam]

I'm not using prisma migrate at all, Prisma is not managing my DB, it's the other way around only in my case. So I update the Prisma schema after making changes to the DB with prisma db pull.

[janpio]

All you did was rename a column from foo to bar (via external SQL changes, then ran prisma db pull) and now a create in Prisma complains about another column name telephone not existing? Can you paste the full output you are getting please?

[kvnam]

Yep, the error message is not very helpful. The database (supabase) returned record "new" has no field "fullName" and Prisma returned this as The column new does not exist in the current database. Supabase has not modified the error I believe, is it because Prisma does not map to Postgres trigger function errors formats..?

[janpio]

Ah, that is super valuable information!

Yes, I expect Prisma does not know this and somehow creates a misleading error message. Can you please open a bug report issue for this? Optimally with a reproduction of how to get to this? Then we could reproduce and schedule fixing this - to hopefully not make more people waste their time in the future on it.

[kvnam]

Sure, I'll raise a bug report issue for this, glad I can help 👍

[snikch]

Just found this via Google. Doesn't look like this was ever fixed? Exact same issue - supabase trigger.

[cesarvspr]

here a trigger using a column that was dropped was causing this