Open frandiox opened 5 years ago
Thanks! Can you share the the User
type from your datamodel?
One approach would be to upgrade your Prisma server. That might or might not fix the error.
@marktani It happens with any model and any search value, not only ids. Even when looking for a string "true" it throws the same. It doesn't matter how many rows or how many columns there are.
In any case, the user type is like this:
type User {
id: ID! @unique
identity: String!
auth0id: String! @unique
email: String! @unique
role: Role @default(value: "...")
firstName: String
lastName: String
createdAt: DateTime!
updatedAt: DateTime!
}
Ok, so it might be a deeplier rooted issue.
For role: Role
, is it an enum? Can you share that as well?
Does User
not have any relations?
It's an enum, yes:
enum Role {
ADMIN
SPECIALIST
MANAGER
}
The user has no relations. As I said, this happens with any model/type. Even with one that has only ID and 4 boolean values.
Ok, I cannot reproduce this in my service. That it happens on all your types indicates an issue with your service/server. Did you already try to upgrade your server?
@marktani If I don't remember wrong, I deployed 1.14-beta originally and then upgraded to 1.14 when it was released. Nothing else after that I think 🤔
Since @frandiox and I have a very similar setup (ref #219), I tested this as well. In general, search seems to work fine for me, though. I did spot one weird issue, and that was looking in the console while searching.
I searched for "name" in my Campaign
model, and the console threw this error:
In my code, CampaignWhereInput
does indeed not support searching for emailsToNotify_contains
:
Not sure if that helps, but I thought I'd mention it.
@jhalborg how does the Campaign
type look like in your datamodel? More specifically, what type is the field emailsToNotify
of?
This is a problem we have as well. I do understand that sometimes data gets out of whack and things like that, but the data browser really should be able to manage these situations with elegance and search effectively.
@marktani
Sorry for the delay, here's the datamodel for Campaign
:
type Campaign {
id: ID! @unique
version: Int!
name: String!
...
emailsToNotify: [String!]!
}
I updated from Prisma 1.14 to 1.19 without issues and now search box works again 🎉
I have the same problem as @frandiox. Tried with the last versions 1.19.0 and 1.20.1 and still have this problem. Since you could solve by updating prisma version, maybe part of the problem is related to my datamodel.
Hi! Every time we use the search feature in Prisma Cloud it throws an error in the console:
Deployed to Zeit Now Prisma version: 1.14 Stack trace in the server:
Two servers with similar setup throw the same errors. Any ideas?