petradonka
commented
2 years ago Hey @justinhandley, what Prisma version are you using locally?
Open justinhandley opened 2 years ago
petradonka
commented
2 years ago Hey @justinhandley, what Prisma version are you using locally?
justinhandley
commented
2 years ago 3.12.0
On Aug 19, 2022, at 3:54 AM, Petra Donka @.***> wrote:
Hey @justinhandley https://github.com/justinhandley, what Prisma version are you using locally?
— Reply to this email directly, view it on GitHub https://github.com/prisma/studio/issues/1008#issuecomment-1220366242, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEXXRK2ZLVFLHLIOTZHU4DVZ44U7ANCNFSM566LCUGA. You are receiving this because you were mentioned.
janpio
commented
2 years ago Prisma is complaining that you have an implicit relationship (both sides just have [] and no explicit fields in the @relation), but are using references in @relation - which is also not valid any more in newer Prisma versions (but was before 4.x I think). Weird thing is that the schema you posted does not actually have that - but the error message does have snippets from such a schema. Can you check that your Prisma Cloud project indeed is using the same schema you have posted? You should be able to see it online when you log in.
justinhandley
commented
2 years ago Hi There,
So, this did uncover an internal issue I have to look into which is that our main branch is way behind develop. I’m not building production any more - when I did it was by pushing to Main - seems like that has changed - so sorry about that.
I created a new instance using our develop branch and it did work.
However, it seems like data browser’s default of asking for 100 records is somehow causing a database timeout - if there are only a couple of records it works, but everything with more than 100 records is timing out for me.
Justin
On Aug 19, 2022, at 7:57 PM, Jan Piotrowski @.***> wrote:
Prisma is complaining that you have an implicit relationship (both sides just have [] and no explicit fields in the @relation), but are using references in @relation - which is also not valid any more in newer Prisma versions (but was before 4.x I think). Weird thing is that the schema you posted does not actually have that - but the error message does have snippets from such a schema. Can you check that your Prisma Cloud project indeed is using the same schema you have posted? You should be able to see it online when you log in.
— Reply to this email directly, view it on GitHub https://github.com/prisma/studio/issues/1008#issuecomment-1221178041, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEXXRKTXJWOVAB7DNDBMOTV2ANNRANCNFSM566LCUGA. You are receiving this because you were mentioned.
petradonka
commented
2 years ago Thanks for the additional info @justinhandley! Based on your local version (3.12.0) and @janpio's details about the error, I think the issue might be that your schema is not compatible with the latest Prisma version.
You're using 3.12.0 locally, but Data Browser in PDP is trying to parse your schema with the latest Prisma version (4.2.1).
I'd suggest to update to the latest Prisma version to make sure Data Browser can handle the schema you have. You might've done something similar already when using the state of your develop instead of main.
Regarding the performance issues with a larger number of records, I think that might be related to having a large number of relations. Does that seem possible based on the data you know you're trying to work with? If that's the case, we'll be rolling out some improvements early next week, which will hopefully fix the issue for you. If not, we can dig into it more and see what could be going on.
justinhandley
commented
2 years ago OK, thanks,
Justin
On Aug 21, 2022, at 9:44 AM, Petra Donka @.***> wrote:
Thanks for the additional info @justinhandley https://github.com/justinhandley! Based on your local version (3.12.0) and @janpio https://github.com/janpio's details about the error, I think the issue might be that your schema is not compatible with the latest Prisma version. You're using 3.12.0 locally, but Data Browser in PDP is trying to parse your schema with the latest Prisma version (4.2.1). I'd suggest to update to the latest Prisma version to make sure Data Browser can handle the schema you have. You might've done something similar already when using the state of your develop instead of main.
Regarding the performance issues with a larger number of records, I think that might be related to having a large number of relations. Does that seem possible based on the data you know you're trying to work with? If that's the case, we'll be rolling out some improvements early next week, which will hopefully fix the issue for you. If not, we can dig into it more and see what could be going on.
— Reply to this email directly, view it on GitHub https://github.com/prisma/studio/issues/1008#issuecomment-1221549349, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEXXRNMEOZPWCYAQMOSMZLV2IXFVANCNFSM566LCUGA. You are receiving this because you were mentioned.
Bug description
My schema:
I think it is telling me to remove the @relation, but if I do that, and I have many many-to-many connects of the same data type to itself, how will it know which one to connect to?
Strangely, I can run Prisma Studio fine locally, just the cloud version throws this error.
How to reproduce
Expected behavior
Cloud version of prisma data browser works like local version?
Prisma information
Environment & setup
Screenshot of page where the problem happened (if applicable)
No response
Prisma logs
Studio version 0.470.0