on conflict mutation gives unexpected result

Question

on_conflict returns unknown argument

new to hasura, tried looking at multiple how to on_conflict, ran mutation from api explorer and from frontend, tried upsert_users (suggest me to change it to insert)

mutation upsert_users {
 insert_users(
    objects: [{
    auth0_id: "iexistindb", 
    name: "somename"}
  ], 
  on_conflict: {
  constraint: users_pkey, 
  update_columns: [last_seen, name]
  }
) {
    affected_rows
  }
}

expected to update the user table if auth0 already exist

solved: used the api explorer analyze, i need to add admin access to enable on conflict mutation. — BatManMightBeReal, Sep 17 '19 at 09:47
Can you add this as the answer to your own question? This will help someone else who has this problem? Thanks! — Gene Z. Ragan, Sep 29 '19 at 23:39
i will tried to figure it out rather new to stackoverflow, but thanks for pointing out :) — BatManMightBeReal, Oct 13 '19 at 17:12

score 1 · Answer 1 · answered Sep 17 '21 at 15:29

1

so i just encountered this now. i had the on_conflict / update_columns but hadn't given update permissions to the role, only insert

answered Sep 17 '21 at 15:29

chrishawn

478
1
4
12

1

You can accept your own answer so it will not be in not-answered – Alex Yu Sep 19 '21 at 05:52

on conflict mutation gives unexpected result

1 Answers1