hi all, we have an app where we want a hybrid of prisma-managed postgres tables and non-prisma managed tables. the latter category is primarily because we’re doing some detailed sql stuff that prisma isn’t yet able to support. we’re running into an issue where prisma seems very eager to delete tables that aren’t mapped in our schema.prisma file. i see a

--create-only

migrate flag that does a dry run for schema migrations but i’m wondering if there’s also a

--dont-delete-tables-you-dont-know-about-pretty-please

flag as well?

Will this help? https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#ignore

possibly. would that require us to provide mappings for all the tables in the schema even if we don’t plan to ever access them via primsa?

I believe so, I haven't used this feature myself

cool, that was going to be my workaround recommendation to the team

@cedric 👋 Currently that’s not possible as the Migrate expects the database to map to the tables defined in

schema.prisma

. There’s a feature request for the same that you can add a 👍 on and your use case as well. For now, I would suggest using introspection as you have tables not just being managed by Prisma.

thanks