Hey there, i want to upgrade my project to the la...
# orm-help
n
Hey there, i want to upgrade my project to the latest version of prisma. This includes changing to the new datamodel. I did this on my dev environment (which is on the same server, so the server is already upgraded) and it works fine. Now I want to make a copy of my production env to test and see if everything works fine. But I can’t find any way to do this. When I try to deploy a new service with the old datamodel file the server complains, that it’s invalid When I just copy the prod database and act like this is a new service my deployment says everything is up to date Any idea how I can do this?
h
You mean you copied the datamodel from dev to prod and Prisma Server is saying that everything is upto date?
n
Yes, at least the way I tried it that’s what happened
With a copy of prod
But I think I copied it wrong
h
So the problem is solved now, or your are still facing some issues?
n
I took a break because I couldn’t figure it out. I’m trying it now again. I just assume that I did something wrong during copying
I want to have a copy of my production service that behaves exactly the same, so I can test if my migrations will work
When I just copy the database, service@prod to e.g. service@test and then I add an entry to the prisma.Project Table
and I copy the latest revision from the prisma.Migration table
Then it says in the playground: Uncaught Error: Mutation fields must be an object with field names as keys or a function which returns such an object.
h
You have run prisma deploy?
n
with the new or the old datamodel?
h
new datamodel
we will need to use --force if you are migrating from old datamodel to new datamodel
n
Ahh, now it works. Before it said “already up to date”
But I just copied it again and I think i might have missed something
thanks for your help