@nilan @nikolasburk @tim2 Think I’ve found a pretty nasty bug here… We have a

User

type with a many-to-many relationship defined with a

Tag

type. The

createUser

and

updateUser

allow us to specify

tags: { connection: [ { id: "..." }, { id: "..." } ] }

which will create a relationship between the user and the specified tags (via

id

). However, when we use

upsertUser

and do the same, it runs successfully but NONE of the connections/relationships are created.

@weakky https://github.com/prismagraphql/prisma/issues/1579#issuecomment-398781606

This was fixed and merged 20 days ago though https://github.com/prismagraphql/prisma/pull/2529. You may have your issue fixed by upgrading, I don’t know on which version it was released though.

thanks for your feedback, @siyfion. We will consider removing the non-working parts from the API. @weakky the PR you mentioned only concerns itself with

connect

,

disconnect

and

delete

, not with

create

,

update

and

upsert

.

Yeah, it’s still very much broken in

1.10

🤔 :

introduce support to execute connect, disconnect and delete within upsert

. Doesn’t this mean that

connect

mutations are now executed within

upsert

mutations ?

I don’t mind that it’s broken, as doing a simple get->update/create is easy in a resolver… What I object too is the fact it makes it look as though it’s all implemented and working, with no error!

I totally see your point, and I agree. I will report back in that issue soon 🙂

I thought we changed the docs to reflect the above?

@nilan sorry, I thought I’d found a huge bug after spending an entire day tracking the issue down… Thought it might have been a regression in

1.10

that needed fixing asap.