Hello everyone, I’m facing this very weird issue w...
# orm-helpm
makarst
10/05/2018, 9:09 AMHello everyone, I’m facing this very weird issue where I did the following:
1. Introduced a new optional Int field to an existing Prisma server
2. Now I want to run a manual migration by using “updateMany” mutation and I get an error “<field> is not defined in the input type”
However, I can see that field defined in Playground. Moreover, I am able to run a regular update mutation (not a batch one) on a single item. Also, I am able to run this batch mutation with a local docker.
Have any of you encountered this type of behaviour? This is really weird.
✅ 1
👍 1
n
nilan
10/05/2018, 12:09 PMit sounds like an outdated schema 🙂
nilan
10/05/2018, 12:11 PMNow I want to run a manual migration by using “updateMany” mutationhow exactly are you trying that? Is it a
curlm
makarst
10/05/2018, 12:36 PM@nilan it did sound like an outdated schema but I’m seeing the field in Playground doc + I can execute a one-of update via
update<ModelName>n
nilan
10/05/2018, 12:50 PMcan you share your service endpoint?
nilan
10/05/2018, 2:41 PMwe resolved this in PM
2 Views