ed
07/29/2019, 8:49 AMed
07/29/2019, 8:49 AMed
07/29/2019, 8:50 AMGamaranto
07/29/2019, 4:12 PMprisma deploy
is very slow on 1.34?matus.congrady
07/29/2019, 4:20 PMconst query = {
games: async (_parent, args, context, info) => {
return context.db.query.games(args, info);
}
}
John M
07/29/2019, 6:09 PMdatamodel.primsa
file. When I try running prisma generate
to generate the TypeScript files, it seems to hang for quite a while. Recently it crashed and there was a report.json file created by node specifying it ran out of memory. I'm running prisma again, this time with more memory: NODE_OPTIONS=--max_old_space_size=8192 prisma generate
. For now it's still churning along, but I'm wondering if there is anything I could be doing better or differently?John M
07/29/2019, 6:16 PMIsaac Weber
07/29/2019, 6:24 PMAndrés Villalobos
07/29/2019, 6:57 PMJehun
07/29/2019, 7:55 PMJehun
07/29/2019, 7:56 PMtype Member {
webhardPay: [WebhardPay] @relation(onDelete: CASCADE)
}
type WebhardPay @db(name: "mmsv_webhard_pay") {
member: Member @relation(onDelete: SET_NULL)
}
John M
07/29/2019, 8:05 PMJohn M
07/29/2019, 8:10 PMJehun
07/29/2019, 8:20 PMMember
✖ The field `webhardPay` must provide a relation link mode. Either specify it on this field or the opposite field. Valid values are: `@relation(link: TABLE)`,`@relation(link: INLINE)`
WebhardPay
✖ The field `member` must provide a relation link mode. Either specify it on this field or the opposite field. Valid values are: `@relation(link: TABLE)`,`@relation(link: INLINE)`
Jehun
07/29/2019, 8:21 PMUser
✖ The field `blog` must provide a relation link mode. Either specify it on this field or the opposite field. Valid values are: `@relation(link: TABLE)`,`@relation(link: INLINE)`
Blog
✖ The field `owner` must provide a relation link mode. Either specify it on this field or the opposite field. Valid values are: `@relation(link: TABLE)`,`@relation(link: INLINE)`
Jehun
07/29/2019, 8:22 PMTotoro
07/29/2019, 10:43 PMtype User {
id: ID! @id
firstName: String!
lastName: String @default(value: "")
email: String! @unique
passwordHash: String
emailVerified: Boolean! @default(value: false)
verifyToken: String
avatar: String
userSource: UserSource!
identities: [Identity!]
createdAt: DateTime! @createdAt
updatedAt: DateTime! @updatedAt
}
type Identity {
id: ID! @id
service: ServiceType!
serviceId: String!
username: String!
email: String!
name: String
accessToken: String! @db(name: "access_token")
tokenType: String! @db(name: "token_type")
expiresAt: DateTime @db(name: "expires_at")
refreshToken: String! @db(name: "refresh_token")
idToken: String @db(name: "id_token")
user: User! @relation(link: INLINE)
}
I'm trying to list identities and get the email from array of identities like this:
const id = await prisma
.user({ id: user.id })
.identities({
where: {
service: USER_SOURCE.GOOGLE,
},
});
console.log(id.email);
When I console.log(id)
, I can see all the values but console.log(id.email);
shows nothing to meTotoro
07/29/2019, 10:46 PMmatus.congrady
07/30/2019, 9:41 AMMarvin
07/30/2019, 9:45 AMauthentication
& authorization
basics (https://www.prisma.io/tutorials/graphql-rest-authentication-authorization-basics-ct20) and there is something I don't understand.
I understand the difference between these two but solves graphql-shield
both of them or just the authorization? I also looked into the graphql-auth
example (https://github.com/prisma/prisma-examples/tree/master/node/graphql-auth).
It seems like I just need graphql-shield
which protects my routes. Is that correct?
Thank you! 🙂James
07/30/2019, 1:39 PMJames
07/30/2019, 1:44 PMTarzan
07/30/2019, 6:56 PMTarzan
07/30/2019, 6:57 PMTarzan
07/30/2019, 6:57 PMJosh
07/30/2019, 8:23 PMfaure
07/30/2019, 10:21 PMfaure
07/30/2019, 10:22 PMfaure
07/30/2019, 10:22 PM{update: object }
, is there a way to automate this?Sanjay
07/31/2019, 12:07 AMError: Couldn't find key postgres-password in Secret prisma/prisma-postgresql