Since the new

prisma generate

doesn't create a separate

prisma.graphql

, how can I import graphql `Type`s in my

schema.graphql

?

in the

where

part of a query, when filtering on an optional date object, do objects who's date is null get included in the results? For example. in this query will users whose

lastFeedLoad

date is null get included?

whats the easiest way to create a graphql server to connect with prisma?

How do I access the server logs of a Prisma Cloud server? I would like to find some more details on a

Whoops. Looks like an internal server error.

I need help with this question: https://www.prisma.io/forum/t/stuck-applying-changes-0-5-upon-prisma-deploy-command/4403

anybody know whats going on here?

Hi! Are there any upgrade or migration docs for moving from 1.12 to 1.16/1.17-beta-1?

Is it a known issue that if I delete a node,

previousValues { id }

is

CuidGCValue(cjlhtfvz56jxi0b45g7fnlpp1)

(instead of

cjlhtfvz56jxi0b45g7fnlpp1

) ?

Hi, just read the blog post about the prisma client beta release and it looks very interesting. I was wondering: What does this mean for prisma bindings and schema delegation? Is the the prisma client supposed to replace bindings and delegation in the future? Or create an easy alternative to them? If I create a gateway server for multiple prisma microservices, should I import the clients generated in the microservices into the gateway instead of creating service bindings/delegating to them?

All examples links from Prisma’s README (master branch) are currently broken (404 redirecting to unknown page). They should redirect to

prisma-examples

repository

I made a doc PR on migrating from Prisma Binding to Prisma Client. If interested, please give it a look and let me know if it works for you! https://github.com/prisma/prisma/pull/3090

Hey folks! This package is still valid? https://github.com/prisma/graphql-transform-schema

I have a

credentials

field in my

Account

type, and I want to remove it from my exposed schema. I was wondering if schema transformation is the way to go.

Is there an upgrade guide for the new Prisma Client , such as going from an existing project with Prisma Bindings to Prisma Client

correction, I just looked 3 posts up and @lawjolla has already submitted a PR. Thank you !

Will Prisma cloud support mongodb anytime soon?

when I do a

where

clause with multiple inputs do I have to surround them with an

AND

or is it implicit?

Hello, I have a use case wherein I’d like to use Prisma deploy to setup my tables, but have all table migrations from then onward handled by a database versioning tool such as Liquibase or FlywayDB. However, I would also still like to be able to deploy my updated graphql schemas to the Prisma service using prisma deploy. I believe I can do this by setting

migrations: false

in the docker-compose.yml, and I thought this issue had gone away (with the help of @sorenbs) but I was wrong and get a series of errors upon doing that and running prisma deploy which do not appear when running prisma deploy without that setting on:

Errors:

  ExampleSetting1
    ✖ The required field `id` is missing and has to have the format: id: ID! @unique or id: UUID! @unique or id: Int! @unique.

 ExampleSetting2
    ✖ The required field `id` is missing and has to have the format: id: ID! @unique or id: UUID! @unique or id: Int! @unique.

  ExampleType1
    ✖ The scalar field `exampleField` has the wrong format: `[String!]` Possible Formats: `String`, `String!`

  ExampleType2
    ✖ The scalar field `exampleField` has the wrong format: `[String!]!` Possible Formats: `String`, `String!`

  ExampleType3
    ✖ The scalar field `exampleField1` has the wrong format: `[String!]` Possible Formats: `String`, `String!`
    ✖ The scalar field `exampleField2` has the wrong format: `[String!]` Possible Formats: `String`, `String!`

Deployment canceled. Please fix the above errors to continue deploying.

I was wondering why these errors show up only during a deployment with

migrations:false

, or perhaps if I can even do an initial deployment of my tables with a prisma service when I have that setting.

Hello everyone 🙂

If I have a many-to-many relation like this:

type Role {
  id: ID! @unique
  name: RoleEnum! @unique
  users: [User!]!
}

enum RoleEnum {
  ADMIN
  USER
}

type User {
  id: ID! @unique
  name: String!
  roles: [Role!]!
}

How can I add a connection from both sides? Will this work?

ctx.db.mutation.updateRole({
  where: {
    name: RoleName,
  },
  data: {
    users: {
      connect: {
        id: userId
      }
    }
  }
})

Hey all, I’m seeing an issue (again) with X-Apollo-Tracing. My graphql endpoint doesn’t accept that header. I can see that this issue was resolved: https://github.com/prisma/graphql-playground/issues/490. however in the source code that header still exists? Not sure if it should be removed or at least made optional. See: https://github.com/prisma/graphql-playground/blob/5b019b862f2a82396b0cccb2020e17dcb6215e7a/packages/graphql-playground-react/src/components/Playground/SchemaFetcher.ts#L62

Thanks guys! I wrote the code, reverted, wrote it again, assuming that I was not properly understanding how the child view works.

Has anyone tried installing prisma using this guide? https://www.prisma.io/docs/get-started/01-setting-up-prisma-new-database-a002/

I’m having an issue with the docker-compose command. It hangs and doesn’t do anything. I’m wondering if it could have anything to do with mySQL, not sure if it’s installed on my mac.

anyone has a good resource on how to test (prisma || graphql) resolvers? I remember seeing an example repo but couldn't find it anymore.

anyone has use

prisma

with an existing postgres db ?

With prisma, are api endpoints for your database automatically generated? In graph.cool they are. I thought prisma did that too but it looks like the resolvers, queries, and mutations are all manually defined in the tutorials I’m looking at.

@jdoyle112 prisma generally is meant to sit between your graphql server and your database, so it looks something like

front-ends

<->

graphql-server

<->

prisma

<->

database

. you can expose prisma directly to your frontends, but then the frontend can pretty much do any database operation, so you’ll want to define and self manage a graphql server that talks to prisma and processes requests from frontends

that graphql server is where you can handle policy/permissions, and youll have to define a schema and resolvers for that “manually”

@patrickdevivo thanks for the explanation, I’m still a little confused though. So prisma offers a graphql api, right? In order to use that, do I need to create any resolvers on my graphql server?