iago
02/17/2019, 10:54 PMmutation {
createUser(
data: {
provider: { connect: { domain: "this.exists" } }
email: "email"
}
) {
email
}
}
It's an internal prisma error, and the mongo error is Unrecognized field in update operation: arrayFilters
FYI connecting though an @id
fails as well.Harshit
02/18/2019, 11:59 AMiago
02/18/2019, 12:31 PMiago
02/18/2019, 1:57 PMtype User {
id: ID! @id
email: String!
provider: Provider! @relation(link: INLINE)
}
type Provider {
id: ID! @id
domain: String! @unique
}
operation: mutation {
createUser(
data: {
provider: { create: { domain: "bla.bla" } }
email: "email"
}
) {
email
}
}
result:
Whoops. Looks like an internal server error.
--- Unrecognized field in update operation: arrayFilters' on server mongo:27017
Harshit
02/18/2019, 1:57 PMiago
02/18/2019, 1:58 PMiago
02/18/2019, 1:59 PMmongo 3.4 91170ab1aa1a 3 weeks ago 374MB
iago
02/18/2019, 2:03 PMiago
02/18/2019, 2:27 PMbit
may be? 🙂Harshit
02/18/2019, 2:28 PMiago
02/18/2019, 2:28 PMHarshit
02/18/2019, 2:32 PMHarshit
02/18/2019, 2:32 PMHarshit
02/18/2019, 2:32 PMiago
02/18/2019, 2:32 PMHarshit
02/18/2019, 2:32 PMiago
02/18/2019, 2:33 PMiago
02/18/2019, 2:33 PMiago
02/18/2019, 2:33 PMHarshit
02/18/2019, 2:33 PMHarshit
02/18/2019, 2:33 PMHarshit
02/18/2019, 2:33 PMHarshit
02/18/2019, 2:34 PMversion: '3'
services:
prisma:
image: prismagraphql/prisma:1.26
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
default:
connector: mongo
uri: '<mongodb://prisma:prisma@mongo>'
mongo:
image: mongo:3.6
restart: always
environment:
MONGO_INITDB_ROOT_USERNAME: prisma
MONGO_INITDB_ROOT_PASSWORD: prisma
ports:
- "27017:27017"
volumes:
- mongo:/var/lib/mongo
volumes:
mongo:
Harshit
02/18/2019, 2:34 PMHarshit
02/18/2019, 2:36 PMiago
02/18/2019, 2:38 PMiago
02/18/2019, 2:39 PMHarshit
02/18/2019, 2:40 PMiago
02/18/2019, 2:48 PMdo4gr