Hi Dear prisma team, I wanted to ask you about creating migrations with primary behaviour of persisting the data in db instead of dropping it. I see you have an issue opened about it here. However it has only 4 thumbs up. So I am wondering why so few people are interested in this? To me this looks quite important 🙂

5 now 🙂 Have you added a thumb?

tru that. I did 😄

In the past I’ve used the

@map

attribute to change model names without having to drop a table. https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#map-1