ℹ️ 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 prismo 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