and as it fans out and scales, i've had it crash my cluster before

Hi everyone 👋

I've got a simple question on how to create an object with an empty array

Previously I'd do:

thing: { create: [] }

but migrating to

prisma2

I'm not sure what I need to do here.

Is anyone aware of any limits to subscriptions in Prisma? We are using subscriptions for a chat feature in our app and we've noticed subscriptions probably don't get called 3 out of 10 times. We suspect a limit at this stage but just wondering if anyone has experienced this and if there are any work arounds.

Im aware that prisma1 questions get almost no answers, yet I'll try. How does one debug prisma 1's performance, e.g. notice whether there is some memory leak or anything. We notice that when performing certain operations, the server gets progressively more and more tired as this operation is executed again, the server gets more and more tired (hinting at a memory leak), yet I wouldnt know where to start debugging this

I’m looking for someone that knows Prisma pretty well and would like to chat on my podcast about it (give an overview of it). How it’s used, why using it, etc. If interested, please reach out to me via DM or at marcelo@themarcelolewin.com - My podcast is here - https://podcasts.apple.com/us/podcast/contentful-creators/id1502912455

Wanted to follow up to see if anyone's gotten Prisma worker nodes to purge cache on schema

for some of our pods it didn't seem like schema propagated properly

I could really use some help figuring out how to increment an integer.

Can’t find anything online

maybe I could

executeRaw

?

2 db operations for this 😕

can you just upsert?

Hey I'm really trying to find an excuse to try out prisma 😄

But I'm stuck with the document database Couchbase and I understand that Prisma isn't going to support Couchbase for quite some time, you need to use something popular like postgres etc..

My question is, can I just setup a repository layer + schema that prisma can use?

is it even worth trying to get a non-supported database to work with Prisma?

has anyone managed to deploy a prisma 1 app (without subscriptions) to zeit now v2?

type User {
  id: ID! @id
  name: String!
  email: String! @unique
  password: String!
  posts: [Post!]!
  userInfo: [Userinfo!]!
  dailyReports: [dailyReport!]!
  inEventCards: [Event!]!  @relation(name: "EventCardAddedBy")
  myEventCards: [Event!]! @relation(name: "EventCardsToUser")
}

type Comment {
  id: ID! @id
  createdAt: DateTime! @createdAt
  name: String
  text: String!
  addedBy: User!
  post: ID!

ERROR: There is a relation ambiguity during the migration. The ambiguity is on a relation between Comment and User. Please name relations or change the schema in steps.

For those running Prisma in production and on the cloud, what type of machine type do you it running on?

does anyone currently run prisma 1 at scale?

I'm having some issues with running at scale, even with 150+ replicas

We are having the same issue.

Prisma 1 just keeps crashing under very light load, we are running 20 replicas

This is interesting @Alan and @Ethan Pursley would you share some metrics about your loads and what you are running it on (vm’s with load-balancers, kubernetes ect ). Only if you’re comfortable with that of course

I'm currently running some load tests where there is a heavy read/write of new data (stuff that wouldn't be cached)

I'm running Prisma on GKE, it has it's own node pool of 20 nodes

with horizontal pod autoscaler, the prisma pod takes too long to initialize and get into a ready state.

prisma seems to be the only thing running into issues for auto scaling