Martin Chełminiak

I've been experiencing a similiar issue. My guess is that it's a problem with Drizzle and custom schema names. Are you also using `schemaName` in the Payload config?

@DanRibbens Thanks for digging in! Even with such `drizzle.config.ts`, the issue persists: ``` import type { Config } from "drizzle-kit"; export default { schemaFilter: ["payload"], schema: ["payload"], } satisfies Config;...

@DanRibbens I've read that creating `anyTable` in `public` schema would fix the Drizzle issue. While it didn't fix it, now it tries to push the tables into the schema, however...

@hansfuchs I believe there is already a fix in progress: [drizzle-team/drizzle-orm#2363 - Fix RQB behavior for tables with same names in different schemas](https://github.com/drizzle-team/drizzle-orm/pull/2363)

Thanks Loïc! This is a blocker for our team too. We're developing a tool entirely made out of CLI commands. There is a way to do everything with Vercel commands:...