@Adil yes, all you have to do is to set a different port in your

docker-compose.yml

like

Reading this repo https://github.com/prisma/specs im probably way more excited than I should 😄

Is there any eta for photon-go? Or ways to contribute

Does anyone know if there's a migration guide for getting off graph.cool? It continues to have outages and issues like https://github.com/prisma/graphcool-framework/issues/577 and little support even for paying users

Running prisma using podman instead of docker, and finding that it is only listening on tcp6 (IPv6) instead of tcp4 (IPv4); seems that NodeJS does this (https://github.com/nodejs/node/issues/18041); is there a way to tell Prisma to listen on a particular IP address? I tried adding “host:” at the root of the config (not in databases) and that does not work.

Guys, it’s been a while so far since we’ve heard at least something from Prisma team (#announcements)

Is the project still maintained?

What are the estimations for the release?

@prilutskiy troll 😂

I wrote an article on how to create a Relay connection with Nexus I would like to share: https://fullstackdatasolutions.com/graphql-how-to-make-relay-connection-type-with-nexus/

hello everyone, I added a secret field to my prisma.yml file and upon deployment, i was taken to the prisma login page in my browser, created an account and i get this error

ERROR: No cluster could be found for workspace '*' and cluster 'default'

. Tried implementing this solution but still doesn't work for me https://www.prisma.io/forum/t/error-no-cluster-could-be-found-for-workspace-and-cluster-default/6402 I have provided my prisma management secret and also management api secret but still facing this issue. Currently running on Prisma CLI version: prisma/1.34.8 (windows-x64) node-v10.16.3 Many thanks.

does the prisma2 datamodel file support dotenv?

Hey all, building an commerce website and I was suggested to use a db transaction to lock the row. This would prevent against two users making simultaneous requests and overselling the product if the stock is low enough. Is there a way to do this currently with prisma or is there a better way to handle what I am trying to do? 😃

hi, can someone clarify this issue for me?

does this mean that prisma client creates n+1 db queries?

I thought that prisma client had a built-in dataloader but this appears to suggest otherwise

! Could not connect to server at http://localhost:4466. Please check if your server is running. Get in touch if you need help: https://spectrum.chat/prisma To get more detailed output, run $ export DEBUG="*"

docker not starting. log Exception in thread "main" java.lang.RuntimeException: Unable to load Prisma config: com.prisma.config.InvalidConfiguration: Only Postgres connectors specify a schema. If they do they also need to specify a database. Other connectors only specify a database.

Is anybody knows when Prisma connector will be ready to connect a neo4j database?

Arrrrgh!!! Am tearing my hair out trying to get the PRISMA_CONFIG accepted in GKE cluster. Exception in thread “main” java.lang.RuntimeException: Unable to load Prisma config: mapping values are not allowed here in ‘string’, line 1, column 32: port: 4466\nmanagementApiSecret: ZDhzazFqN2VoZDhCQjJOczhTYmEK\n ...

Hey guys I just found out that ‘forwardTo’ from prismabinding doesnt work with graphql yoga anymore. Is there any library that does the same thing?

Is this slack not active anymore? I don’t see any questions getting answered.

hello everyone. I'm fairly new to prisma and had a question about many-to-many relationships. I am trying to represent a following/follower relation between users, where each relation has a boolean blocked field. Here is an excerpt from datamodel.prisma:

type User {
  id: ID! @id
  username: String! @unique
  email: String! @unique
  phoneNum: String @unique
  firstName: String!
  lastName: String!
  password: String!
  profilePicture: String
  status: Status! @default(value: ACTIVE)
  followers: [User!]!
  following: [User!]!
  createdAt: DateTime! @createdAt
  updatedAt: DateTime! @updatedAt
}

type Following {
  id: ID! @id
  follower: User!
  followed: User!
  blocked: Boolean! @default(value: false)
  createdAt: DateTime! @createdAt
  updatedAt: DateTime! @updatedAt
}

When I run

prisma deploy

, I get an error saying that the relations

followers

,

following

(on

User

),

follower

,

followed

(on

Following

) don't have names. If anyone could help me with figuring this issue out, I would be forever grateful as I have been struggling with this for a couple of weeks now. My current workaround is that I deleted the

followers

and

following

fields on

User

and instead wrote resolvers for them as computed fields and named the

followed

and

follower

relations on `Following`:

// resolvers/User.ts
    t.list.field("followers", {
      type: "User",
      resolve: async ({ id }, args, ctx) => {
      const fragment = `
        fragment FollowerUserInfo on User {
          follower {
            username
            email
            firstName
            lastName
            profilePicture
            id
          }
        }
      `;

        const rows: User[] = await ctx.prisma.followings({ where: { AND: [{ followed: { id } }, { blocked: false } ] } }).$fragment(fragment);
        const followers = rows.map((elm: any) => elm.follower);
        return followers;
      }
    });

// datamodel.prisma
type Following {
  id: ID! @id
  follower: User! @relation(name: "Follower")
  followed: User! @relation(name: "Followed")
  blocked: Boolean! @default(value: false)
  createdAt: DateTime! @createdAt
  updatedAt: DateTime! @updatedAt
}

Moreover, I am using the following versions of Prisma-related dependencies:

"dependencies": {
    "apollo-server-express": "^2.9.3",
    "express": "^4.17.1",
    "graphql": "^14.5.4",
    "graphql-middleware": "^4.0.1",
    "graphql-shield": "^6.1.0",
    "nexus-prisma": "^0.3.8",
    "prisma-client-lib": "^1.34.8"
  },
  "devDependencies": {
    "@types/express": "^4.17.1",
    "@types/graphql": "^14.5.0",
    "@types/jest": "^24.0.18",
    "@types/node": "^12.7.4",
    "@typescript-eslint/parser": "^2.3.0",
    "apollo-server-testing": "^2.9.3",
    "jest": "^24.9.0",
    "ts-node": "^8.3.0",
    "ts-node-dev": "^1.0.0-pre.42",
    "typescript": "^3.4.5"
  }

Please let me know if this makes sense or not or if there's a more efficient way of doing things. Thanks!

👋

@Ismail Arafa the GitHub API deals with exactly the same pattern of followers, IIRC. The relations are called Connections there and importantly Following is the inverse of Follower (in other words a different Relation) … see https://apis.guru/graphql-voyager/ and load up the GitHub schema for a visual

How to connect to a DB that only secured connections are allowed?🤷‍♂️ ➡️ https://www.prisma.io/forum/t/google-cloud-platform-database-only-secured-connections-are-allowed-to-connect-to-this-instance/7947

Apolgies if this has been asked before but i am unable to find the answer. When I try and get the schema using 'get-graphql-schema --json ENDPOINT_URL > schema.graphql' the only output i get is the readme in the schema.graphql file. What am i doing wrong?