tonevast.blogg.se

1. #GRAPHQL AS A UNIVERSAL DATABASE ABSTRACTION HOW TO#
2. #GRAPHQL AS A UNIVERSAL DATABASE ABSTRACTION CODE#

Prisma Studio is different from a typical database GUI (such as TablePlus ) in that it provides a layer of abstraction which allows you to see your data represented as it is Prisma ships with a powerful database GUI where you can interact with your data: Prisma Studio. Therefore, if you restart the server, the feed query will keep returning the same links. However, the difference is that this time the submitted links will be You can send the same feed query and post mutation as before. As usual, run the following command in your terminal to start the GraphQL server:

#GRAPHQL AS A UNIVERSAL DATABASE ABSTRACTION CODE#

With these code changes, you can now go ahead and test if the new implementation with a database works as expected. This is not a problem as Apollo Server is capable of detecting, and automatically resolving any Promise object that is returned from resolver functions. This is because all Prisma CRUD operations are asynchronous. You may also have noticed that newLink is an object of type Promise.

These methods are auto-generated based on your model definitions in So, to summarize, Prisma Client exposes a CRUD API for the models in your datamodel for you to read and write in your database.

As arguments, you’re passing the data that the resolvers receive via the args parameter. You’re calling the create method on a link from your Prisma Client API. Similar to the feed resolver, you’re simply invoking a function on the PrismaClient instance which is attached to the context. hackernews-node/src/index.js post : ( parent, args, context, info ) = > ) return newLink That’s all a bit theoretical, so let’s see how it looks in action 💻 Updating the resolver functions to use Prisma Client This means that we can attach an instance of Prisma Client to the context when initializing the server and then access it from inside our resolvers via the context argument! A really helpfulįeature is that you can already write to the context at the moment when the GraphQL server itself is being initialized. Thus, it is basically a means for resolvers to communicate. The context argument is a plain JavaScript object that every resolver in the resolver chain can read from and write to. Remember how we said earlier that all GraphQL resolver functions always receive four arguments? To accomplish this step, you’ll need to get to know another one – the context argument! The first thing you need to do is import your generated Prisma Client library and wire up the GraphQL server so that you can access the database queries that your new Prisma Client exposes. Wiring up your GraphQL schema with Prisma Client

#GRAPHQL AS A UNIVERSAL DATABASE ABSTRACTION HOW TO#

In this section, you’re going to learn how to connect your GraphQL server to your database using Prisma, which provides the interface to your database.