Alright ryan.

Is there a way to delete something based on two identifiers?

Ie:

await prisma.rosters.delete({
										where: {
											id: raid.id,
											raider_id: user.id
										}
									})

Hey there - Can I do an upsert with a where clause where the id is a compound key? How would that work?

E.g. if I use something like

@@id([a, b])

, how can I do upserts on those models?

🤗 “What’s new in Prisma (v2.6.0)” live stream starts in 10 minutes!*  *to learn about new releases, planned features, and other interesting bits from the Prisma world.

When using Nexus, what's the equivalent to stringArg() for JSON? I can't find jsonArg() ...

Hey all, updating from 2.5.0 to 2.6.0, it seems like Prisma started treating optional fields in my DB as required. Is this bug or some breaking change?

Hi, so going through the documentation of prisma v1.34 I noticed that an OR operator is not supported for mongo DB so I thought about doing a raw query but that too seems to not be supported. Is the only solution to this really to query twice and combine the two queries before returning? That wouldn’t be the end of the world if it was temporary… are there any changes coming soon to prisma 1.34 or prisma 2 in regards to mongo DB? Thoughts and advice would be appreciated.

I just wanted to post this again to ask more people, is this the correct way to test prisma? https://www.notion.so/nahtnam/Testing-with-Prisma-and-Jest-4263872c3a73439f8a16bdd27a604ce5 Is there a better way (preferably with Factories) or more advanced mocking?

hi, i have this issue trying to update . That field is type datetime . what means Object(weak) ?

What's the status on migrate? I understand it's still experimental, but are people using it? I guess I'm wondering how close it is to being stable

Hey folks, I'm going live in about 10 minutes! We'll be building a simple fullstack ticket app using Next.js and Prisma. We will use Heroku to host our database, handle authentication with Auth0, and deploy our finished app to Vercel. Come say hi!

Hello guys, I’m using

graphql-yoga

with prisma 2, and I have some issues when creating items with

Enums

I got this error when I execute my mutation :

Argument type: Provided value 
{
  set: [
    'CLOTHES'
  ]
}
of type Json on prisma.createOneItem is not a enum.
→ Possible values: Type.CLOTHES, Type.SHOES, Type.ACCESSORIES, Type.DECORATION

anyone have an idea on how enums works with mutations ? thanks you

I have genuinely no idea what this means.

Introspecting based on datasource defined in prisma/schema.prisma …
Oops, an unexpected error occured!
[/rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libcore/str/mod.rs:1942:47] byte index                                                                1 is out of bounds of ``

Hey there! How can one define Prisma middlewares when using the nexus-plugin-prisma?

Is there any admin tool that is built with prisma2 in mind? Something like wp-admin for those of you who are familiar with Wordpress

Or a nice boilerplate project to achieve similar functionality

Any Graph.cool folks can help me get one last DB copy of a customers site. So I can backup the latest data with that version on Prisma2

Hi! Trying to upgrade from prisma1 to prisma2 and got stuck on the step where it wants me to "Fix 1-1 relations by adding

UNIQUE

constraints" It seems like some of the contraints it wants me to add are "switched" This is the problamatic datamodel

type Absent {
   treatment: AbsentTreatment!
    @relation(link: INLINE, name: "TreatmentOnAbsent", onDelete: CASCADE)
}

type AbsentTreatment {
  absent: Absent! @relation(name: "TreatmentOnAbsent", onDelete: SET_NULL)
}

It wants me to run:

ALTER TABLE "default$default"."AbsentTreatment" ADD UNIQUE ("absent");

But there is no absent field on AbsentTreatment with this model.. Should I instead run the following?

ALTER TABLE "default$default"."Absent" ADD UNIQUE ("treatment");

Or should i update the prisma1 datamodel?

I am running Prisma 2.3.0 and it seems whenever I do migrations they do not update the database.

When using

prisma migrate

, what are people using to deal with indexes and other "non-Prisma" stuff for migrations? A separate migration setup?

What's the preferred method to create multiple entities at once in Prisma2? Just call

create

multiple times in a

Promise.all?

Any reason for deprecation of connect/disconnect?

Thinking of building an adapter to use Prisma to back FeathersJS at some point

this place seems quiet

I don't know but it seems like my issue got deleted from github so I'm posting it here, maybe it was just too silly. but I need serious help.

I'm getting this weird error message after running docker-compose up -d

I'm running this on WSL Ubuntu 18.04