I'm wondering if he is using a different database than I do (I use Mongo), as it has been stated that lists should be specified as [Typename!]! - but that may be a quirk of the Mongo implementation (and so could the Inline thing be for that matter)

I don't see any particular errors in the schema. I have seen the error in question, but then definately due to missing naming (and all relation in the example above have names). However, it sounds like, prior to this change with aliasesOf, there may have been an unamed relation? If that relation received a name as part of the addition of aliasesOf, then that sounds like a possible reason. In that case, deploy a change where the old relation get a name, then an new deployment with the new field.

I can't seem to deploy to my prisma 1 cloud development instances, or access the service's dashboard on app.prisma.io. Just get an eternal loading spinner Get this error when trying to deploy:

ERROR: Whoops. Looks like an internal server error. Search your server logs for request ID: eu1:cky5k9iwnm80j0913ooqzwsht

{
  "data": {
    "addProject": null
  },
  "errors": [
    {
      "message": "Whoops. Looks like an internal server error. Search your server logs for request ID: eu1:cky5k9iwnm80j0913ooqzwsht",
      "path": [
        "addProject"
      ],
      "locations": [
        {
          "line": 2,
          "column": 9
        }
      ],
      "requestId": "eu1:cky5k9iwnm80j0913ooqzwsht"
    }
  ],
  "status": 200
}

 Anyone else experiencing this?

Has anyone gotten a new mac with the M1 chip and had problems trying to get the prisma 1 image to work locally? We just got the latest docker update that says non-arm architecture images should work by default without needing Rosetta anymore. It's up and running, and the logs look the same as the logs on my mac that isn't an M1 chip. But it keeps freezing anytime I attempt to do a deploy or dry run. And any attempt to send a query through just hangs as well.

Working on a Prisma 1 to 2 migration and would greatly appreciate some help... I have several Prisma 1 "one way" relations, e.g.

type User {
   avatar?: File
}

type File {
  url: String
}

However, it looks like that's not allowed in Prisma 2. Prisma 2 wants to see something like...

model User {
   avatar: File?
}

model File {
  userId:  String?
  user:    User? @relation("UserFile", fields:[userId], references: [id])
}

But I get the error...

The column `File.userId` does not exist in the current database.

The problem is that there's no underlying database structure for that relation and I can't migrate my db because my Prisma 2 schema and migration database are so far out of sync. (I want to get Prisma 2 working and then deal with the migration problem) Is there any stop gap to push through this? Did I somehow miss this in the migration docs? 😬

For those running prisma1 and mongodb in production, what kind of connection count (in the connection pool) do you see between prisma and mongodb? I have a setup in GCP where prisma is on the inside on the db elsewhere, so connections are routed through cloud NAT. There are (configurable) limits to how many ports can be open (each connection is mapped through one port) on the router, and with two instances of prisma, this low limit was reached, causing connection errors and general havoc.

I can add that just making a bunch of requests manually over a few minutes, makes the each instance have about 60 connections open.

Hi, I am not sure if this is the right place to be asking a technical question. But, here it goes anyway.

prisma1 deploy ▸ Could not connect to server at http://localhost:4466. Please check if your server is running. how do I sort this problem out.

@Douglas Maxton Presumably you run your prisma in a docker, so you can do "docker ps" to check which containers are up on your machine. There should probably also be a related db container. Did you start prisma using docker-compose? If you did, depending on whether you used the -d switch or not, things may have stopped if you e.g. closed the terminal window you were using for it.

Hey, has this repository been deleted recently? github.com/prisma/prisma-client-lib-go

hi, I ran prisma1 deploy and it redirect me to app.prisma.io asking for permission. Any idea why?

ℹ️ <!channel> This message is for anyone using Prisma 1 Cloud (free or paid). If you don't use Prisma 1 Cloud and have never signed up at prisma.io/cloud (login: app.prisma.io) feel free to ignore this message. 🚨 Due to Prisma’s new focus on the open-source ORM and the Prisma Data Platform, we will officially sunset Prisma 1 Cloud on September 1st, 2022. However, Prisma 1 Open Source (self-hosted) is still in maintenance mode for now. 🚨 👉 Find more details in the sunset notice.

I am trying to set up Prisma 1 in Kubernetes as described in the link below. This one is however from Prisma 1.17, and I am a bit uncertain if all of it is true for 1.34. https://techblog.commercetools.com/prisma-horizontal-scaling-a-practical-guide-3a05833d4fc3

What are the differences betwen prisma and prisma-prod images?

I guess I found out, was only confused by the revisions and failure handling in gke

@Lars Ivar Igesund Damn, you're still in the Prisma 1 game strong. What's stopping you with upgrade?

@Maciek K That is a complicatedish answer, but the main reason now is time. I am the main development resource of this startup, and except for shorter periods, I don't have the ability to work full time on it. That may change as/if we get investors, but we have to actually launch and get customers prior to that happening. But also, I have no idea how much work it will be. We use mongo, which only recently became an option with newer Prismas, the schema is different (and more complex is my impression), and the API-generation options are different. This suggests to me that it will be a non-trivial amount of work to upgrade.

Hello everyone, I am actually fixing an old project of my client using prisma1. I am having trouble with the management API on the prisma cloud which I cannot make it work. Could one of you help me ? I am loosing my mind on it. I redo the tutorial of the documentation and I still got the problem. What I am doing wrong ? • prisma1 login --key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx • prisma1 init • Select the prisma1 cloud with mysql, then press enter for everything • export debug="*" • prisma1 deploy The error is on the deploy

Do you have access to the server logs?

Also note the official messages further up in the channel, prisma 1 cloud is sunsetting later this year.

I dont know how to access the server log. I am using the prisma 1 cloud. How do I access the log ? Any documentation about that ?

Does prisma1 reset work through the prisma-prod image? Using the cli says it does, but there is no obvious result in the db.

Hello, I am trying to export and import data from one service on https://app.prisma.io to another. But I am having trouble to understand how to do. Apparently, there is an endpoint /export and /import. I am trying something like this but it's not working :

curl '<https://eu1.prisma.sh/xxxxxx/demo/dev/export>' -H 'Content-Type: application/json' -H 'Authorization: Bearer xxxxxxxxxxx'

But it always redirect me to the playground

Any help would be very appreciated 😛 Thanks in advance

Hey, do we have any Prisma 1 MongoDB users in here? We're working on a migration guide and I have some questions for you 🙂

Hello, I heard that Prisma 1 cloud is gonna close on September 1st. I don't use Prisma 1 cloud but a heroku server but I do use prisma 1. Will I still have access to my database at http://app.prisma.io ? Thank you

set the channel topic: 🚨 This is a * community only * channel! Prisma 1 Cloud will be sunset on Sep 1st, 2022. Prisma 1 Open Source (self-hosted) is in maintenance mode for now.

Hello, I have exported my database and I am actually trying to import my database back using prisma1 export and prisma1 import. I have not changed the schema between import and export. I received this error that I dont understand what that mean, what I need to do.

Hi guys, we are running prisma1 on heroku with a postgres Database. We currently have the Performance 2 Postgres plan and 2 of the Performance M dynos for prisma1 server. And even with this every other day we have an issue where a lot of requests timeout and we have to restart the dynos manually. This is our config + JAVA Env Variable: port: $PORT managementApiSecret: xxxx databases: default: connector: postgres migrations: true connectionLimit: 180 uri: ${DATABASE_URL}?ssl=1 JAVA_OPTS = -Xmx2G We have tried upgrading our server further but we are shooting in the dark in this case. Does anyone have any ideas on what the issue might be or how can I even start to debug something like this? We are planning to move to prisma3 but we aren't there yet, we just got to keep prisma1 going til the end of the year