Heya, bumping my question from yesterday. I'm having trouble following the guide for the expand-contract pattern in the context of a rolling deploy where two versions of my prisma client are receiving production traffic at the same time. Steps 1-6 work just fine, but Step 7 asks me to remove a column from my schema. When I do that, the new prisma client expects the column to be removed whereas the old prisma client expects the column to be present. During the rolling deploy, code reliant on the old prisma client will throw an error like below, even if I don't refer to that column anywhere in my code. Any advice on what to do here? Is there a way for me to exclude a field from my prisma client without modifying the underlying database schema?

Invalid `prisma.user.findUnique()` invocation:
  The column `User.removedField` does not exist in the current database.

Hey Luke 👋 Can’t you use this

@ignore

attribute? https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#ignore Here’s a related Feature Request for Expand and Contract pattern: #4727