deactivateduser
10/05/2019, 5:15 PMdeactivateduser
10/05/2019, 5:53 PMAdam Leith
10/05/2019, 11:58 PMtype Request {
id: ID! @id
notes: [String] @scalarList(strategy: RELATION)
}
is erroring on prisma deploy
with: Request
✖ Valid values for the strategy argument of `@scalarList` are: RELATION.
Anyone know how I can fix this?lucid_frog
10/06/2019, 1:14 AMimport { prismaObjectType, makePrismaSchema } from 'nexus-prisma'
Module '"../../../../path/to/project/node_modules/nexus-prisma/dist"' has no exported member 'prismaObjectType'
Any idea?Heade
10/06/2019, 8:25 AM@scalarList
is used for relation mutationsHeade
10/06/2019, 8:27 AMDan Hollick
10/06/2019, 1:22 PMprisma deploy
? It runs in the console as expected but my Service doesn't reflect the data model changesJames
10/06/2019, 1:48 PMJames
10/06/2019, 3:11 PMprisma export
and prisma import
. That mostly works, but it gets to some relations and complains: "Failure inserting into relationtable Response with ids StringIdGCValue(ck0vyh1zd04v7079202qab9co) and StringIdGCValue(ck0w7w1sh05ov0790a9ntrvdo). Cause: .SQLIntegrityConstraintViolationException: (conn=828922) Cannot add or update a child row: a foreign key constraint fails (`james-6ee4db~instaquiz@dev`.`Response`, CONSTRAINT `Response_ibfk_3` FOREIGN KEY (`answer`) REFERENCES `Answer` (`id`) ON DELETE SET NULL)"
James
10/06/2019, 3:13 PMJames
10/06/2019, 3:29 PMlucid_frog
10/06/2019, 3:33 PMKyle Melton
10/06/2019, 9:31 PMCannot return null for non-nullable field Office.publicServants
I'm only getting their id
. All offices have 1 or more PublicServants
and all PublicServants
have `id`s.deactivateduser
10/06/2019, 11:08 PMJames
10/07/2019, 5:00 AMJames
10/07/2019, 5:01 AMTobias
10/07/2019, 5:19 AMYong Yuan
10/07/2019, 5:32 AMyolen
10/07/2019, 8:13 AMprisma deploy
i get this message $ /home/jens/Desktop/onlaw.dk/node_modules/.bin/prisma deploy --no-seed
Deploying service `default` to stage `default` to server `local` 914ms
Warnings:
Global
! You are migrating from the old datamodel syntax to the new one. Make sure that you understand the listed changes because the semantics are different now. Then perform the deployment with the `--force` flag.
If you want to ignore the warnings, please deploy with the --force flag: $ prisma deploy --force
Read more about deployment warnings here: <https://bit.ly/prisma-force-flag>
should i worry?Martí Crespí
10/07/2019, 8:23 AM--force
tag.Stijn de Koning
10/07/2019, 9:49 AMStijn de Koning
10/07/2019, 9:49 AMconst updatedUser: User = await prisma.updateUser({
data: {
role: 'ADMIN',
},
where: {
id: 'cjli512bd005g0a233s1ogbgy',
// AND status: 'ACTIVE'
},
})
Stijn de Koning
10/07/2019, 9:49 AMStijn de Koning
10/07/2019, 9:50 AMKishan T.
10/07/2019, 10:57 AMJosef Henryson
10/07/2019, 4:55 PMFransjo Leihitu
10/07/2019, 5:29 PMgem
10/08/2019, 10:44 AMDan Hollick
10/08/2019, 10:51 AMinno
10/08/2019, 3:34 PM