Thank you, I'm running the queries from the prisma upgrade and I'm having an issue with updating the enums. Query:

CREATE TYPE "default$default"."Type" AS ENUM ('BULK', 'SHOP', 'TBC');
ALTER TABLE "default$default"."Order" ALTER COLUMN "type" SET DATA TYPE "default$default"."Type" using "type"::"default$default"."Type";

ERROR: default for column "type" cannot be cast automatically to type "default$default"."Type" SQL state: 42804 Any ideias why this is happening? I'm still new to postgres

Hi folks! I'm trying to run

prisma1 deploy --no-migrate

but I'm receiving migration validation errors like this one:

The underlying column for the field "status" has an incompatible type. The field has type "Enum" and the column has type "String"

. I have two questions: 1. Why if I use the --no-migrate flag prisma is running migration validations? 2. Why the error says that Enum is not compatible with String? Prisma creates Enum datamodel field as varchar(191). Is this a bug?

Hi folks. Which is the best way to do deploys on prisma1? What if I have traffic to my db while the deploy is in progress? I have problem with that and mutations. Mutations try to lock the table but the manager did it before so my mutations start to fail with the error

Deadlock found when trying to get lock; try restarting transaction

.

🚨 Hello <!channel>! On September 1st, 2022 we will change the status of Prisma 1 Open Source Software from “maintenance mode” to “deprecated”. This means that we will archive the Prisma 1 GitHub repo and we will no longer provide fixes for critical bugs, develop new features, or provide support for user issues - more information here. As a reminder, on September 1st we will also sunset Prisma 1 Cloud (free and paid) (login: app.prisma.io) - more information here.

set the channel topic: 🚨 This is a * community only * channel! On Sep 1st, 2022, Prisma 1 Cloud will be sunset and Prisma 1 Open Source (self-hosted) will be deprecated.

prisma1 delete not only removes the service from the prisma servere but it also delete the database. why isn't docummented this behavior? and also, is there a way to only remove the prisma service and NOT the database?

Is there any recommendation to set CONNECTION_LIMIT ? I saw documentation for current versions of prisma but for prisma1 I did not find any advice

This is a final reminder that you have until September 1st, 2022 to close your Prisma 1 Cloud account (prisma.io/cloud). We will also archive the Prisma 1 Open Source GitHub repo and we will no longer provide fixes for critical bugs, develop new features, or provide support for user issues - more information here.

Hi @channel, We are having trouble finishing the migration from Prism1 to Prisma3. Our prisma3 is using a GraphQL connect to a PostgreSQL on AWS. We did most of the work but are stuck on a few last errors (schema ambiguity). We are looking for help (either freelancer and/or expert Prisma3). Any recommendations? CC @Kevin Justal, our lead developper. Here is the type of errors we are getting.

ERROR: There is a relation ambiguity during the migration. Please first name the old relation on your schema. The ambiguity is on a relation between CustomerSubscription and Plan. Please name relations or change the schema in steps.

{

"data": {

"deploy": null

},

"errors": [

{

"locations": [

{

"line": 2,

"column": 9

}

],

"path": [

"deploy"

],

"code": 3018,

"message": "There is a relation ambiguity during the migration. Please first name the old relation on your schema. The ambiguity is on a relation between CustomerSubscription and Plan. Please name relations or change the schema in steps.",

"requestId": "local:cl6diaxtq001t0818wi9ql9jp"

}

],

"status": 200

}

Hey guys and and girls. So I'm currently working on upgrading out code to prisma 3 or 4 from prisma1 and I've noticed a diference between the schemas that prisma 4 generates compared to 1. So fields with the type Int[] prisma one makes an extra table. ie: Product_prices While prisma4 has that field in the same table. (Product) What's the best way to upgrade this data type? Is there a way to keep using the old tables or will I need to copy all the data over to the parent table (product)? Any ideas ? Thanks 🙂

Good Afternoon Gentlemen. I have another question regarding prisma1 upgrade. Currenlty I'm updating the datamodel and I'm not sure how to do this relation in prisma4. Any ideias? adultVersion: GarmentType @relation(name: "GarmentTypeAdultChild") childVersion: GarmentType @relation(name: "GarmentTypeAdultChild", link: TABLE)

Anyone on here that are actually running prisma1 in an active k8s cluster? As I slightly ramp up requests (there are some bursts from dashboard types of frontends) , the prisma nodes crash/throw exceptions after reaching a max (500) of mongodb threads. There is nothing that resembles CPU or memory issues. Is this some form of configuration that I can do anything with? Why isn't 500 threads enough for what is still a fairly low number of requests?

@andrewicarlson FYI

Waited till the last week to migrate off of the prisma 1 cloud..... wish me luck

I've migrated from 1 to 3, but when I db pull, my field names are singular and capitalized. E.g. Prisma 1 schema type User { … posts: Post[] } Vs Prisma 3 db pull model User { … Post: Post[] … } What am I missing?

Hi, I've asked this question last year, but I'm not sure if Ryan is still at Prisma 😄 Anyone?: https://prisma.slack.com/archives/C0152UA4DH9/p1637163031019400

Hello all, As mentioned here: https://prisma.slack.com/archives/C0152UA4DH9/p1656690261741449 The prisma 1 cloud will be sunset. We are in the middle of a migration but our production is still using prisma1 self-hosted on our private server on AWS. We are using the app.prisma.io to look at our data but not using anything thing cloud related. Will we be affected by the change ?

hi folks, wondering if anyone knows how to set the connection pool timeout for prisma1? i see the docs for current version here but haven’t been able to find a similar reference for prisma1

@Jeff Gardner What database do you have? For mongodb, this should be settable via the connection string

ℹ️ Sept 1st, 2022, we officially sunset Prisma 1 Cloud and deprecated and archived Prisma 1 OSS. Prisma 1, the open source library, was created more than 5 years ago, and Prisma 1 Cloud has served our users and customers for more than 4 years as well - we're very grateful to everyone who supported us throughout these years! 💚 Our Prisma 1 Docs and the archived repository will stay online, but the Prisma team will no longer provide fixes for critical bugs, develop new features, or provide support for user issues. Resources: ✨ Upgrade your app from Prisma 1 to Prisma 2+ (You’ll no longer need Prisma 1 Cloud since Prisma 2+ doesn’t require the Prisma server anymore). ✨ Switch to self-hosted Prisma 1 Open-Source ✨ Try the next-generation Node.js and TypeScript ORM. ✨ Optimize Prisma for production workflows

Hi, since yesterday, Sept 2nd, 4pm UTC, my self-hosted prisma1 spams my logs with some error

com.prisma.akkautil.http.FailedResponseCodeError: Server responded with 503.

(every 30s average). I think this is related to the app.prisma.io shutdown. How can we prevent these errors in our logs?

Hey everyone, Im upgrading to Prisma 2 and I keep getting this error when using prisma-upgrade: SyntaxError: Expected "(", ")", ",", or [_A-Za-z0-9] but ":" found.

Does anyone know what I can do to fix this?

Hey Everyone! I was wondering if anyone could give me insight on the plans for the prisma docker image on docker hub (prismagraphql/prisma). As I know prisma1 has recently been sunset recently but I've seen nothing on the future for the docker image as it's currently depend on until we have the ability to move from Prisma 1 - Prisma 4. Are the docker images on docker hub going to be deleted any time is essentially what I need to know?

Hi everyone, I’m pretty much lost on the upgrade and don’t know where to start anymore, any help would be appreciated. Even an RTFM pointing to the right doc would be appreciated because I’m lacking the confidence I’m reading the correct one and investing the time in the right place. So here’s the situation. I have a project I started in mid-2019. I then decided to use Prisma, Apollo and GraphQL with a MySQL db. Below an excerpt of my package.json:

"dependencies": {
		"bcryptjs": "^2.4.3",
		"dotenv": "^6.0.0",
		"graphql": "14.4.2",
		"graphql-yoga": "1.18.0",
		"jsonwebtoken": "^8.3.0",
		"prisma": "^1.18.1",
		"prisma-binding": "^2.1.4"
	}

It was deployed in prod with a bit of data, but I paused the project end of 2019 and I lost access to the account… So that’s gone. It was running locally but in the meantime, I changed computer (new mac M1) so I don’t have a local DB already there. Now I tried naively following the docs but: 1. I’m struggling to find the correct endpoints to set up for different reasons. a) I didn’t document enough it seems so I’m lost between yml and env files and b) I understood I needed an arm patch which seems to modify a bit the setup 2. I am definitely stuck at the

npx prisma db pull

step. I tried running

npx prisma db pull --schema=./src/generated/prisma.graphql

instead and this gives me validation errors. Which sends me on a sort of loop of documentation, because to validate it needs to run, to run I need to upgrade Maybe I didn’t try hard enough to run Prisma1 to begin with, but what set me off on the path to directly upgrade was that I understood I needed a new docker-compose.yml set-up. I have no shame to say I am very confused 😅 I haven’t touched all this in 3y and at the time I sort of rushed the project in a few months on the side, I don’t do backend so often and my memory is bad. I documented my code, but I did not document well enough to handle this kind of issues 😄 I’m willing to invest the time to re-up the project though! The last thing I was trying was to manually edit the prisma.graphql file, but I don’t really have the dictionary to translate since the doc assumes the bulk of it got translated by the db pull command. Pls send help 😛rismo-gif:

Hey so we were waiting to consider going to prisma2 based on how all of the new nexus plugin stuff, which is now called

nexus-prisma

for prisma2 was going to shake out. I know it’s in early preview right now, but I noticed you guys just archived the graphql-nexus channel, which makes me believe that path might be getting abandoned. Can I get any more future clarification on whether there is still any sort of commitment to having that whole story supported moving forward with prisma2. I know it’s not a main focus, but I need to know if it’s going to ultimately going to be semi-abandoned or not because it doesn’t align very much at all anymore with where prisma is heading, and so I should plan my migration path to be without the ability to continue to have auto-generated CRUD based on my schema or not. I know that there are other threads historically that have attempted to address this, but they’re pretty old now and I am curious if anyone else is in the same boat as us in this community channel, or if @nikolasburk would be willing to point me to another more recent discussion about this topic in a github thread somewhere or mention some thoughts here.

@tmoney We are somewhat in the same position, and while we probably won't do the conversion just yet, I was looking at building a related product, just using fresher versions of everything (we're using react-admin and material-ui on the frontend, both of which has gotten a new major version (the latter turning into mui) since we created most of the code). Anyway, I found this thing - https://github.com/panter/ra-data-prisma - which I came to search for a new prisma dataprovider for react-admin. Looking in the packages directory here, it seems to in practice have created some alternatives, including typegraphql.

When that is said, I think I saw some comments just a few days ago, that there would be some official news on the nexus-prisma plugin stuff soon.

Hmm, maybe I'm misunderstanding what panter is doing there - I see nexus-prisma-plugin being mentioned, also some of it hasn't been updated much for the last year (while the overall project has had releases in the last few months.

Always best to import and export using PG Dump or equivalent of the database you are using