Zak
04/16/2019, 4:25 PMBjoern
04/16/2019, 5:56 PMs1nc4p
04/16/2019, 8:04 PMcaptaindaylight
04/16/2019, 8:05 PMSandeep Goyal
04/16/2019, 8:47 PMhenrique
04/16/2019, 10:00 PM_some
? e.g. this query returns all my projects
await context.prisma.projects({
where: {
owners_some: { id: userId }
}
})
I want the opposite now to return the projects I’m not associated it. I tried owners_not
but with no luck. Thoughts?CCBCodeMonkey
04/17/2019, 12:57 AMwhere: {id_contains: "blah"}
to prisma, say for SQL injections?CCBCodeMonkey
04/17/2019, 12:58 AMsapkra
04/17/2019, 3:28 AMmutation
and not just the node
. When I try it I'm just getting a type error.
Types of property 'subscribe' are incompatible.
Type '(parent: object, args: any, ctx: Context) => Promise<AsyncIterator<UserSubscriptionPayload>>' is not assignable to type '(root: object, args: any, ctx: Context, info: GraphQLResolveInfo) => AsyncIterator<any>'.
Property 'next' is missing in type 'Promise<AsyncIterator<UserSubscriptionPayload>>' but required in type 'AsyncIterator<any>'.
Nitin Sharma
04/17/2019, 5:30 AMCCBCodeMonkey
04/17/2019, 7:45 AMCCBCodeMonkey
04/17/2019, 7:45 AMprabhat kumar sharma
04/17/2019, 8:19 AMprabhat kumar sharma
04/17/2019, 8:19 AMprabhat kumar sharma
04/17/2019, 8:20 AMprabhat kumar sharma
04/17/2019, 8:21 AMprabhat kumar sharma
04/17/2019, 8:21 AMrdc
04/17/2019, 9:12 AMconst Admin = {
profilePic:{
fragment: 'fragment userId on Admin { id }',
async resolve(parent, args, { prisma }, info) {
const s3Object = await prisma.query.s3Objects({
where:{
admin:{
id: parent.id
}
}
});
return s3Object.length > 0 ?
{
bucket: s3Object[0].bucket,
region: s3Object[0].region,
key: s3Object[0].key
} :
{
bucket: null,
region: null,
key: null
};
}
}
};
rdc
04/17/2019, 10:27 AMresolvers
that prisma server created?Dario Villanueva
04/17/2019, 3:39 PMVote
, I get an error when trying to run prisma deploy
I ~/w/hackernews-node prisma deploy
Deploying service `hackernews-node` to stage `dev` to server `prisma-eu1` 208ms
Errors:
Link
✖ One field of the type `Link` must be marked as the id field with the `@id` directive.
User
✖ One field of the type `User` must be marked as the id field with the `@id` directive.
Vote
✖ One field of the type `Vote` must be marked as the id field with the `@id` directive.
Deployment canceled. Please fix the above errors to continue deploying.
Read more about deployment errors here: <https://bit.ly/prisma-force-flag>
Dario Villanueva
04/17/2019, 3:40 PMcedric
04/17/2019, 4:21 PM/var/lib/postgresql/data
which you can map to an external filesystem. does prisma have something similar?Mahmoud El Kotoury
04/17/2019, 4:34 PMZak
04/17/2019, 5:18 PMZak
04/17/2019, 5:22 PMMahmoud El Kotoury
04/17/2019, 5:31 PMquery {
user(id:"%USERID%") {
email
}
}
This prisma graphql query is translated to this mysql query , I got from the logFrancis John
04/17/2019, 6:01 PMERROR: database "prisma" already exists
. Any ideas on how to get around this?jdoyle112
04/17/2019, 6:57 PMUser
must be marked as the id field with the @id
directive.jdoyle112
04/17/2019, 6:57 PMcedric
04/17/2019, 7:01 PMprisma-nexus
against two separate prisma services. for context, we need to talk to two database schemas, so due to this issue we've created two separate prisma services: https://github.com/prisma/prisma/issues/1622.
this results in two prisma.ymls which are each generating their own nexus-prisma.ts
. however, each file contains the following code:
declare global {
interface NexusPrismaGen extends NexusPrismaTypes {}
}
bc this is in the global namespace, it results in one set of nexus-generated types overriding the other. i'm uncertain of the motivation for using the global namespace here, but i'd be super interested if anyone has any suggestions for getting around this (or if it's a bug that should be filed). we really like working with prisma but i feel like this multi-schema thing is resulting in workarounds layered on workarounds. /cc @weakky @Nick Drane