Can someone help me troubleshoot why I am getting the following error when running a basic query on the client playground? Error:

Cannot return null for non-nullable field DeviceConfig.device.

Datamodel

type Device {
    ...
    model: String! @unique
    ...
    configs: [DeviceConfig] @relation(name: "DeviceConfigs", onDelete: CASCADE)
  }

  type DeviceConfig {
    id: ID! @unique
    device: Device! @relation(name: "DeviceConfigs", onDelete: SET_NULL)
    name: String!
    ...
  }

Query

{
  deviceConfig(id:"cjqigyian00ef0d206tg116k5"){
    name
    id
    device{
      model
    }
  }
}

Resolver

deviceConfig: async (parent, { id }, context, info) => context.prisma.deviceConfig({ id }, info)

Result

{
  "data": null,
  "errors": [
    {
      "message": "Cannot return null for non-nullable field DeviceConfig.device.",
      "locations": [
        {
          "line": 5,
          "column": 5
        }
      ],
      "path": [
        "deviceConfig",
        "device"
      ]
    }
  ]
}

--- When I run the following query on the Prisma API playground it returns Query

{
  deviceConfig(where:{id:"cjqigyian00ef0d206tg116k5"}){
    name
    id
    device{
      id
      model
    }
  }
}

Result

{
  "data": {
    "deviceConfig": {
      "name": "Standard",
      "id": "cjqigyian00ef0d206tg116k5",
      "device": {
        "id": "cjqigxzs600e60d20sdw38x7p",
        "model": "7530"
      }
    }
  }
}

anyone got a recommendation on hosting my app.. its prisma/apolloserver, redis, and next.js for the frontend

I would like a staging server, and a prod server that I can scale up, with continuous deployment...

really don't want to manage my dbs

heroku seems like a great fit but its really pricey

hi there, sometime i confuse. prisma endpoint it’s my API endpoint?

prisma endpoint is the prisma endpoint, usually you create your own graphql endpoint which sits on top

that endpoint talks to the prisma endpoint

its like a business logic layer

Hello and Happy new year to all folks. 😉 I'm starting the year by looking for a solution to add dynamic prisma services with related authorization/permission/role. Any ideas without using a graphql-yoga/apollo on the top of each service or this is for now the only solution?

Hi there 👋 You just said guys which excludes our non-male friends 🙂 We are an inclusive community, please use an alternative like everyone, folks or fellow humans instead. Read more in our Code of Conduct: https://github.com/prisma/prisma/blob/master/CODE_OF_CONDUCT.md

slackbot [9:00 AM] Hi there 👋 You just said guys which excludes our non-male friends 🙂 We are an inclusive community, please use an alternative like everyone, folks or fellow humans instead. Read more in our Code of Conduct: https://github.com/prisma/prisma/blob/master/CODE_OF_CONDUCT.md WHAT THE HELL?

Would you like to link me to a dictionary of Prisma-approved words I'm allowed to use, please?

if you can prove there is at least 1 female here, and that she was offended, i'll apologize

Upon giving this message to my left-wing friends, they are pointing out that hu*man* is also sexist, perhaps you should re-write your SJW bot to include the preferred phrase of "hu-people", thank you.

Hi everyone. What role plays prisma? Lets say, I have next.js application, and I am going to use apollo server 2 to serve graphql API over Postgres. Where (in the request chain) prisma daemon will be running? What for?

I think my Box type from TypeScript is mixing with prisma Box type. How can I solve it?

Have you had problems like this with prima and TS? 😄

Hi.

I'm wondering, why is there no

insertManyX

mutation?

This is what I'm doing now:

await Promise.all(
    apiMarkets.map((market) => {
      return apolloClient.mutate({
        mutation: upsertMarket,
        variables: market,
      })
    }),
  )

it would be really cool if prisma added built in redis support to cache most used queries

similar to rails ORM caching

👋 I wondering if this is possible in a

.graphql

seed file?

Prisma generates CRUD for data model types. Is it possible to disable mutations and leave only queries/subscriptions?

Model's

WhereInput

are not behaving as expected in my GraphQL queries, anyone know how to get around it or is it a bug? I have a user with ID

5c2eb7d56344590009c22341

and when I query a user with

id

,

id_in

,

id_lt

,

id_gt

,

id_lte

,

id_gte

,

id_not

,

id_not_in

I get the expected results, but not with

id_contains

,

id_ends_with

,

id_starts_with

,

id_not_contains

,

id_not_ends_with

,

id_not_starts_with

. For instance, this returns an empty users array

{
  users(where: {id_ends_with: "c22341" }) {
    id
  }
}

What's weird about this is that it's only happening with ID, the rest of the fields are returning the expected results.

section “set up prisma with existing database”, does it mean that prisma can read my existing database schema and produce graphql schema out of it?

How do I seed multiple files one by one into prisma? And in case one fails the other is still be able to work?