Prisma

The list already exists, only the ListElement is new.

They are completely separated in my frontend, so I create the lists in another step.

-.txt

Okay, but wouldn't the id of ListEntry be equal to the id of the list?

it depends on what you are returning there.  Are you returning the list or the entry?

This mutation should generate a new ListEntry with a randomly generated id, a task, that is given by the frontend and an association to an already existing list, with an id that is already given in the frontend.

it should probably be `listId: $listId` and `$listId: ID!`

the first returned id will be the id of the ListEntry

Oh i didn't know I could reference on the Id of an associated field like this.

<@U8L2D9TMJ> I will try this out real quick.

you'll obviously have to write the resolver accordingly

Sorry about that <@U4SHZAY64> :slightly_smiling_face:  Unrelated question -- I'm working on integrating the Shopify GraphQL API.  I've read this entry here: <https://blog.graph.cool/graphql-schema-stitching-explained-schema-delegation-4c6caf468405>, but does anyone know of any sample repos or tutorials on how to implement schema stitching with Prisma?

you can do schema stitching in app server, i don't think that prisma can schema stich

I mean schema stitching in the app server with prisma as one endpoint and shopify as the other

<https://github.com/graphql-binding/graphql-binding-github> you can see here how its done for github, you can do same for shopify i think

but i never tried it, but looks pretty straight forward

Sorry <@U4SHZAY64>, I didn't know how to create one.

Oh, awesome! You always learn something new! :100:

<@U8S8FUZ9R> <@U8L2D9TMJ> Thank you both for your help! :+1: :100: I'm gonna dig myself into the documentation some more. Do you know of some good reference for learning the basics, besides the official documentation?

graphcool docs are great for basic graphql <https://www.graph.cool/docs/reference/graphql-api/overview-abogasd0go>

You can run examples there and try a lot stuff

The blog is also helpful sometimes: <https://blog.graph.cool>

hi guys is it currently possible to do aggregations using prisma like avg, sum, etc ? or is it possible to make the raw sql query at least?

I've got another question for you guys... :wink:
How are the requests counted? I mean the requests, that are set to be the limits between the different billing plans. I'm currently using the free plan, as my project is still in building status, but even tough I create new entries on graph.cool trough API calls and fetch dozens or even hundreds of entries while testing, the request counter stays at 0.

Do regular fetches even count as request or are they ignored in this case? If polls are included in these 100000 allowed requests, my guess would be, that the limit would be reached quite fast, with a relatively small user group. I'm currently refetching the contents of my subpages every 5 seconds, to get the changes on the server, for example.

<@U0RQY0KK5> Could you answer me about this or show me a reference to an explanation? I'm currently trying to evaluate the possible costs for using graph.cool exclusively for my project and don't understand how this count actually works.
Thanks in advance! :slightly_smiling_face:

Any freelancers looking to pickup 10-20 hours a week for 2-3 months? Our stack: graphcool-framework, apollo, react, redux, material ui, etc. DM me for details, thanks!

I think <@U6CQFMGBF> <@U5P82S230> freelance

Hello, does anyone have any idea on how to go about grabbing a value and updating it when creating a new node on pre-Prisma (The older Graphcool)? AKA, grab the most recent count and add one to it when creating a new node.

guys can anyone tell me if the @isUnique directive is own to Graphcool related projects but not actually a thing in original graphql itself?

and if so, what’s the approach to make a @isUnique directive for normal graphql?