cant find anything about it online

if anyone has any ideas here please tag me so i get notified. thanks in advance

A file was commented on

@Jenkins no error output

lol. figured it out. my authentication failed because there is no jwt being passed 😛

when all else fails start commenting out lines until its happy! fast parrot

i had written the context wrong. req / res need to be destructured to be accessed. all in the clear now!

Woop!

request as an object property of...request. not sure i follow the logic but at least i got it working!

I have a mutation that creates

Action

then connect

members

to this

Action

. And I have a subscription for creating

Action

on frontend. When

Action

is created I receive it on frontend but without

members

because it didn't have time to be connected. Any ideas how can I fix it? Mutation - https://gist.github.com/SilencerWeb/004c51fa4156059c121a5d722f0bd5eb

Hi guys, anyone with a guide to deploying prisma to digital ocean manual for prisma above 1.7

It seems i'm not able to create multiple entries of a type when seeding.

mutation seed {
  createUser(data: { username: "Foo" }) { id }
  createUser(data: { username: "Bar" }) { id }
}

There is no createMany. I could split it into multiple mutations, but then i can run only one of them by name. How do i do this? Edit: Okay, 2 more minutes of searching would have sufficed. Found it in one of the examples:

mutation seed {
  user1: createUser(data: { username: "Foo" }) { id }
  user2: createUser(data: { username: "Bar" }) { id }
}

It seems i've encountered a bug on cursor based pagination that is fixed in a newer version. How do i actually update prisma? 🙂

I assume it's enough if i update the devDependency and also update the base docker image in my docker-compose to the same version?

HI guys not sure if this is the right place for this type of query but is there anyway to fire a updateMany mutation with different data for each id passed or would i need to fire off multiple mutations?

Hey guys, i am new to Prisma. trying to understand how to set it up and i am kinda confused. So i want to run a local Prisma server instead of relying on Prisma Cloud. i have my local Prisma API running in Docker exposed on port 4466 and its working fine. Now, as i understand, you have to have another GraphQL API which would be the "main" one, which would query the Prisma API via graphql-bindings in the resolvers. I used graphql cli to generate a react-fullstack-graphql boilerplate. That boilerplate comes with a connection set up to Prisma Cloud. How would i change it to use my local Prisma API? Hope someone can point me in the right direction.

What is the health-check endpoint for Prisma server?

Given a schema (snapshot) of

type TaxonomyValue {
  id: ID! @unique
  identifier: String! @unique
  profiles: [Profile!]! @relation(name: "ProfileTaxonomyValues")
}

type Profile {
  id: ID! @unique
  name: String
  taxonomyValues: [TaxonomyValue!]! @relation(name: "ProfileTaxonomyValues")
}

I'm trying to retrieve records which match on multiple

taxonomyValues

as below:

query {
  profilesConnection(
    where: { taxonomyValues_every: { identifier_in: ["value-a", "value-b"] } }
  ) {
    aggregate {
      count
    }
    edges {
      node {
        name
        taxonomyValues {
          identifier
        }
      }
    }
  }
}

It's only returning me records which have both

taxonomyValues

(only

value-a

and

value-b

), not records which have

value-a

and

value-b

, as well as other ones. I basically want to match profiles on all requested

taxonomyValue

, even if they have other values. Any ideas?

Has anyone used dotenv-cli with prisma?

Hi ! Is there someone to help me out with my first prisma app ? 😄

hi - loving GraphQL! Getting going building a schema and sync/deploying to postgres....2 questions...

why do the tables have "default$default" in front of them, we want the database to be easily queried with SQL for analytics and other things outside the graphQL API, dont want weird table names...

type User{ id: ID! @unique firstName: String! middleName: String lastName: String! dob: DateTime createdAt: DateTime! updatedAt: DateTime! deletedAt: DateTime email: String! @unique password: String disabled: Boolean @default(value: "false") failedAttempts: Int! @default(value: "0") locale: String! @default(value: "en") } type Organization{ id: ID! @unique name: String! createdAt: DateTime! updatedAt: DateTime! deletedAt: DateTime marketingUrl: String supportEmail: String supportPhone: String parentOrg: Organization @relation(name: "ParentOrg", onDelete: SET_NULL) }

also seem to be having issues creating proper indexes, composite indexes, and self references.... example schema..

from this I would expect user email has a unique index put on it (anyway to declare that?)

I'd also expect organization table to just have a parentOrgId as foreign key, not need some ParentOrg separate table as its a one to one optional to list a parent org that allows for building hierarchy...

looks like SQL Pro for Postgres is showing this error on indexs for user also, weird...