If you want to write into a db using insertOrUpdate strategy, you cannot specify column to be used at on conflict and is assuming that is the primary key.

That isn't useful on tables with unique columns but no primary keys (for example with postgres with timescaledb extension, your primary key is an index and not and specific column)

Could I specify a column to be used to looking for a conflict or set an ON CONSTRAINT clause?