set the channel description: Everything around Prisma 1

@nikolasburk @Ryan did you guys figure out a way to migrate a 1-n @relation(link: TABLE)? https://github.com/prisma/prisma/issues/1937#issuecomment-621103677

Can anyone offer advice on scaling the Prisma backend server? I found that subscriptions between the Prisma server itself and my

graphql-yoga

-based server stopped working correctly when I increased the number of instances that Prisma server runs on.

I have discovered this issue which seems to explain how to scale Prisma: https://github.com/prisma/prisma1/issues/2850

We just successfully migrated from Graphcool to Prisma 1.34

👴

Hi! Is there a way to tell the prisma vscode extention that my prisma schema is using Prisma 1? It kinda breaks the linting 😅

I read in a comment on a github issue that prisma 1 had an SQLi test suite.. Is it open source? @sorenbs

While following the How To GraphQL

hackernews-node

tutorial, a couple issues came up and I was hoping to verify the behavior I saw with the Prisma team. First, the

AuthPayload

in the schema.graphql file appears to be misconfigured since the

user

field is defined as having a required

String!

argument. However, when using the

signup

mutation, an error is returned indicating that

Field \"user\" must not have a selection since type \"String!\" has no subfields.

This is because the query provided in the tutorial has the two fields from the

AuthPayload

as return values. So, I updated the schema for the user field to include

User!

. Now, when I execute the

signup

mutation, it performs as expected. However, when an attempt is made to use the

login

mutation, this message is returned:

Variable '$where' expected value of type 'UserWhereUniqueInput!' but got: {\"email\":\"<mailto:alice@prisma.io|alice@prisma.io>\"}. Reason: 'email' Field 'email' is not defined in the input type 'UserWhereUniqueInput'. (line 1, column 8):\nquery ($where: UserWhereUniqueInput!) {\n       ^

I am using Prisma1 without

prisma client

in my resolvers. Eg:

async addresses(parent: any, args: any, ctx: any, info: any) {
    const list = await ctx.db.query.addresses(args, info)
    return list
  }

Should I upgrade to

Prisma client

first? or

prisma2

first?

How to deal with the error

Error Cannot return null for non-nullable type

. I added a new attribute 

name!

  in the data model file and then did

prisma generate

and

prisma deploy

. When I query, it gives the above error

I’m trying to migrate to Prisma2. I’m trying to introspect my Prisma1 MySQL database in local environment. So I deploied my Prisma1's datamodel to local MySQL server but I can’t find the newly created databse. What is the default database name created by Prisma1 with the following docker-compose.yml?

version: "3"
services:
  prisma:
    image: prismagraphql/prisma:1.34
    restart: always
    ports:
      - "4466:4466"
    environment:
      PRISMA_CONFIG: |
        port: 4466
        databases:
          default:
            connector: mysql
            host: mysql
            port: 3306
            user: root
            password: password
            database: drcha
  mysql:
    image: mysql:5.7
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: password
    volumes:
      - mysql:/var/lib/mysql
volumes:
  mysql: ~

Hi there! I'm using the

forwardTo

function to bypass graphql server with prisma and I was thinking if its possible to use

forwardTo

with queries/mutations having different custom names rather than using the names which are already present in prisma.graphql (generated).

For example:

const Query = { items: forwardTo("db") } // `items` keyword is defined in our prisma.graphql

what if we want to have a query of any custom name, (say

message

) and forward it to

items

type?

Hi everybody! I'm trying to get started with Prisma by running

prisma init

, with an existing MySQL database running locally, but when I do this I get the following error -

TypeError: Cannot read property 'startsWith' of undefined

. Does anyone have an idea of what this could be?

Hello everyone I’m trying to deploy my first project on heroku. Locally I’ve successfully connected my project to mongodb atlas and generated schemas on remote DB. then, I’ve deployed the app to heroku via Git. now, I’m not getting if my endpoint url must still remain localhost:4466 or I have to change to the remote heroku one. If I try the latter, I receive a 404 error warning me that it cannot POST on /management. when I run locally

prisma deploy

I’m getting an exception:

ERROR: GraphQL Error (Code: 404)

{
  "error": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Error</title>\n</head>\n<body>\n<pre>Cannot POST /management</pre>\n</body>\n</html>\n",
  "status": 404
}

I’m not getting this because I set the secret key both on prisma.yml than on docker-compose.yml. Am I missing something? It seems an auth error but it could be related to mongo itself?

I’m noticing now that locally,

prisma init

defines a set of local mongo dbs, something that currently I don’t have on the remote db

I’m just confused, because if I use the remote DB wich contains only my deployed schemas, it works with endpoint localhost:4466. On the other side, if I try to run it with the remote heroku endpoint, I’m getting the error

hi guys! I have a table in mysql that I want to build my api around, but Prisma seems to be looking an autogenerated table called

default@default

. Is there a way to change tables that Prisma looks at?

Help - My Prisma1 instance (deployed using app.prisma.io) suddenly stopped working. I’m getting an error:

Detail: User does not have CONNECT privilege.

- not sure if anyone sees something similar?

Hi everyone I’m getting this exception on trying prisma 1 deploy:

ERROR: GraphQL Error (Code: 404)

{
  "error": "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Error</title>\n</head>\n<body>\n<pre>Cannot POST /management</pre>\n</body>\n</html>\n",
  "status": 404
}

Any suggestion?

Hi, does anyone have a good guide to follow to deploy a prisma 1 service to AWS? Is this the recommended one: https://v1.prisma.io/tutorials/deploy-prisma-to-aws-fargate-ct14#deploy-a-prisma-service-to-the-new-server

Hi. We just migrated our database to Yandex Cloud and restored existed database there. And we have strange error with prisma. It could not connect to database, while I can connect to it via dbeaver and view all data. The errors are:

org.postgresql.util.PSQLException: ERROR: odyssey: cf65a9f0be57b: user blocked

org.postgresql.util.PSQLException: ERROR: relation "Migration" does not exist

Hello, what would happen if you change a field from name relation to inline relation? (does the named relation create an underlying table??)

when i was trying prisma deploy i was getting these error !

hello?

apparently, this should be the right place to ask...

a new file prisma.graphql should generate but that was not generating ...

hello ?