ON CONFLICT DO UPDATE asks for `target` column but not stated in docs.

[mafuyuuu1]

According to this example, if I do the same as what the example says, I'm getting an error.

await Account.insert(
      Account(
          number=account.number,
          balance=account.balance,
          token=account.token,
          password=account.password,
          device_id=account.device_id,
            )
    ).on_conflict(
            action="DO UPDATE",
            target=Account.number, # Adding this will fix the error but not included in the example in the documentation.
            values=[Account.token],
 )

asyncpg.exceptions.PostgresSyntaxError: ON CONFLICT DO UPDATE requires inference specification or constraint name
HINT:  For example, ON CONFLICT (column_name).

[dantownsend]

Thanks for reporting this. Which version of Postgres are you using? If no target is specified, then it should target all constraints on that table. I wonder if it's a Postgres bug, or something with the SQL that Piccolo is generating.

[mafuyuuu1]

Which version of Postgres are you using?

I'm using the latest Postgres Docker, which is 17.6

If no target is specified, then it should target all constraints on that table

I just read the documentation on postgres and it says:

conflict_target
Specifies which conflicts ON CONFLICT takes the alternative action on by choosing arbiter indexes. Either performs unique index inference, or names a constraint explicitly. For ON CONFLICT DO NOTHING, it is optional to specify a conflict_target; when omitted, conflicts with all usable constraints (and unique indexes) are handled. For ON CONFLICT DO UPDATE, a conflict_target must be provided.