Pedro Roque
06/23/2022, 12:50 PMCREATE 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 postgresMatias
06/24/2022, 2:46 PMprisma1 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?Matias
06/27/2022, 8:31 PMDeadlock found when trying to get lock; try restarting transaction
.Vladi Stevanovic
07/01/2022, 3:44 PMVladi Stevanovic
07/01/2022, 3:45 PMMatias
07/05/2022, 2:31 PMMatias
07/21/2022, 3:13 PMVladi Stevanovic
08/05/2022, 11:49 AMQuentin Gilon
08/08/2022, 3:31 PMERROR: 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
}
Pedro Roque
08/16/2022, 11:11 AMPedro Roque
08/18/2022, 2:46 PMLars Ivar Igesund
08/19/2022, 1:03 PMVladi Stevanovic
08/23/2022, 3:12 PMAaron Markle
08/24/2022, 3:31 PMlawjolla
08/26/2022, 4:44 PMMaciek K
08/29/2022, 12:27 PMKevin Justal
08/30/2022, 7:27 AMJeff Gardner
09/01/2022, 5:17 PMLars Ivar Igesund
09/01/2022, 5:20 PMVladi Stevanovic
09/02/2022, 6:50 AMCHaBou
09/03/2022, 6:33 PMcom.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?Jonty Coertzen
09/05/2022, 8:29 AMJonty Coertzen
09/05/2022, 8:30 AMWilliam Bray
09/07/2022, 8:18 AMMaxime
09/26/2022, 3:56 PM"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:tmoney
09/28/2022, 9:13 PMnexus-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.Lars Ivar Igesund
09/28/2022, 9:27 PMLars Ivar Igesund
09/28/2022, 9:27 PMLars Ivar Igesund
09/28/2022, 9:30 PMPedro Roque
10/13/2022, 4:54 PM