Is it possible to persist manual changes done to the prisma.schema file? After introspect I have some ignored models so I add a unique identifier to them but after introspecting again, the models are also ignored again

As introspection maps the database, I don’t think it’s possible to persist a unique identifier, but I’ll let @janpio confirm.

Oh, so you add a

@unique

to one of the fields so the table can be used in Prisma, and after the next Introspection that is removed again and the tables ignored? Correct understanding of the situation @Daniell?

Yes

Yeah, then the only solution is to actually change the database to reflect that or have some script you run each time to fix your schema after manual Introspection.

is there any example with sqlserver with Azure SQL

Thanks I will look into fixing that