I am just curious -> is there any alternatives for Prisma?

cough feathersjs

“Feathers is a batteries included but entirely optional minimal web application framework.”

Maybe you got it wrong, but prisma is not even web related

It is, roughly, an orm

Hello! Does anyone is having that issue https://github.com/prisma/prisma/issues/4483 on an self-hosted server (fargate + aurora, v1.32 with secret) ? As a workaround connecting the server to the prisma cloud works, but does anyone has another solution ?

Does anyone else having problem to get response from Graphcool support? Trying to chat with them on Intercom in console.graph.cool but didn’t get a response in over 3 hours.

Prisma has two new stable releases (1.30.4 and 1.32.2). How long will Prisma keep two stable releases? I suppose Prisma 1.30 is still maintained because of issues with Datamodel 1.1

Has anyone had a problem with graphql-yoga and prisma and not being able to run any schema queries? See this issue: https://github.com/prisma/graphql-yoga/issues/561 Am absolutely baffled!!!

Does anyone know how to get rid of warnings regarding directives? for instance

Unknown directive "id".GraphQL: Validation

. I am using VS code

@Josef Henryson They don’t respond for days. Things were way better when Nilan was there. @schickling doesn’t seem to give a damn either. Overall pretty disappointing.

Is there an easy way to expose the Prisma client’s pagination options (e.g.

first, last, skip, after, before

) on the GraphQL schema/resolvers? Tried doing something like

resources: (parent, args, ctx, info) => prisma.resources(args, info),

in my resolver and

type Query { resources: [Resource] }

in my schema but the graphQL playground does not show any filter/sort options. Do I need to do something like

type Query { resources(first, last, blah, blah...): [Resource] }

in my schema for each query?

How to upgrade prisma server deployed on fargate: I have

managementApiSecret: ${PRISMA_MANAGEMENT_API_SECRET}

in

docker-compose.yml

(have deployed prisma in docker on AWS using prisma deploy on fargate tutorial and connected to RDS) Question: I need to upgrade server to

1.32

. How to do something like

docker-compose ... -e .env

? (I was reading comments which suggest that

prisma deploy -e .env

takes care of this; that's why I didn't noticed this when deploying) Docs:

docker-compose pull -e.env

won't work similarly. [https://www.prisma.io/docs/prisma-server/deployment-environments/docker-rty1/]

Looking for Prisma resources. We are a startup and looking to take our React-Native app in production. we looking for someone who has experience with Prisma and Mongodb in production environment. Please ping me if your interested

I try to connect to Prisma server (a docker container) from a nodejs server app container. I run

prisma deploy -e .env.prod

but an error show up:

▸    prisma:4000/my-app/prod is not a valid endpoint. It must start with http:// or https://

`prisma.yml`'s content:

endpoint: ${env:PRISMA_END_POINT}
datamodel:
  - common.graphql
generate:
  - generator: typescript-client
    output: ../src/generated/prisma-client/
hooks:
  post-deploy:
    - prisma generate --endpoint ${env:PRISMA_END_POINT}
    - npx nexus-prisma-generate --client ./src/generated/prisma-client --output ./src/generated/nexus-prisma

`.env.prod`'s content:

PRISMA_END_POINT=prisma/my-app/prod

prisma

is the name of a service in

docker-compose.yml

So does it mean I should create a network for my services, then assign static ip for each service? Something like that:

version: "3"
services:
  my-app:
    restart: always
    build: ./m-app/
    networks:
      - my-net
  prisma:
    image: prismagraphql/prisma:1.32.2
    restart: always
    networks:
      my-net:
        ipv4_address: 192.168.0.2
networks:
  my-net:
    driver: bridge
    config:
      - subnet: "192.168.0.0/24"

Can someone please explain why there is (1) datamodel.prisma (2) graphql.schema (3) resolvers containing ~ same information as 1 and 2? I’m not including the generated schema. Should we expect more and more repeating schemas to be added?

There can be some repetition, but a little repetition doesn't cost much. The datamodel.prisma defines your data model and the graphql.schema defines your outward facing API. You can avoid some repetition by importing your generated graphql.schema in your graphql.schema

Is there any good Info on running my db, prisma server, AND prisma client from one docker compose setup?

To add to @Noah ‘s question, does 1) your data model and 2) the outward facing API have to be identical? If not, why are they different?

Hello, what alternative to Cloudinary do you know? I've read about imagekit but I don't know if this accepts PDF, videos and word files too

is it possible to get aggregate counts on a subfield of many nodes? for instance...

type Company implements Node {
  id: ID!
  date_founded: Int
  description: String
  image: CompanyImage
  country: Country
  name: String!
  slug: String!
  website: String
  jobs(
    where: JobWhereInput
    orderBy: JobOrderByInput
    skip: Int
    after: String
    before: String
    first: Int
    last: Int
  ): [Job!]
}

can I query all companies and get the number of jobs associated with each company? Something kind of like the following...

# Write your query or mutation here
query {
  companies {
    name
    jobsConnection {
      aggregate {
        count
      }
    }
  }
}

Hi, how do you host a mongodb prisma server? I mean I know how to connect it to my database and all but, how do i host my prisma server. Do I have to use docker or are there other ways?

@Sean Urgel just docker afaik. you can use prisma cloud servers at app.prisma.io if you want to quickstart without setting up docker. the demo servers are free. they also have integration with heroku

Hey! I'm making a Vue app with

vue-apollo

, and I need to get many `group`s from one query. I can't make a

groups

query because it would error completly even if only one group failed. How do I generate a query that gets all groups individually?

basically programmatically multiplicate the following query:

query getGroups($auth: [GroupAuth!]!) {
  id1: group(auth: $auth[0]) {
    id
  }
  id2: group(auth: $auth[1]) {
    id
  }
}

Quick question: when doing

prisma introspect

, the generated schema has

field: [Type]

instead of the original

field: [Type!]!

. Did the

!]!

become optional?

Does anyone know how to use a forked version of the prisma CLI? I forked the entire project to fix an issue in the Go generator, but I can't seem to find a way to use yarn or npm to install a project from a sub directory in a GitHub repo. I found a few issues that have been open for years, and it doesn't look like they'll be resolved any time soon. I also came across Lerna, but it looks like the package itself needs to be setup to use. I can see if I can add the configuration files for it in my forked version, but I'm just wondering if there is a better way

hey guys, anyone has any clue on how to fix this : https://www.prisma.io/forum/t/i-cannot-update-a-users-permissions-in-prisma-web-console/6569/10

How does a mutation like createUser in schema know to associate itself with the model User? We don't specifically define the relationship between createUser and User. I could rename createUser to createMember and it'll still work, but how?