porsager / porsager/postgres

Dynamic on conflict definition

Open
#1,025 2 comments 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
8.7k
Forks
374
Avg merge
11d 16h
Merged PRs (30d)
1

Description

I am struggling to set up the SET part of my on conflict definition dynamically.
Everything else working smoothly, but failing to pass upsert information.
Would welcome any help.

const targetTable = "test"
const columns = ["id", "name", "geometry"]
const onConflict = { keys: ["id"], update: ["name", "geometry"]}

await sql`
  INSERT INTO ${sql(targetTable)} ${sql(data, columns)}
  ON CONFLICT (${sql(onConflict.keys.join(","))}) DO UPDATE
  SET ${sql(onConflict.update.map(column => `${column} = EXCLUDED.${column}`).join(",")};
`

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the provided JavaScript SQL template against PostgreSQL and inspect how the client handles dynamic values in the ON CONFLICT SET expression. Compare the behavior with the documented interpolation rules; done means the dynamic upsert information works as intended or the limitation is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, postgresql
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.