| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tim Starling <tstarling(at)wikimedia(dot)org>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Upsert error "column reference is ambiguous" |
| Date: | 2025-04-28 15:21:55 |
| Message-ID: | CAKFQuwYQYsLhn-oCXi7dVg=k2sd_D9i7yu+LDHBMwYYXcM6i+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, April 28, 2025, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> AFAIK, "ON CONFLICT" is a Postgres-ism. Exactly which constructs
> in exactly which other databases are you citing as precedent?
>
I confirmed the SQLite reference from the original email.
“The upsert above inserts the new vocabulary word "jovial" if that word is
not already in the dictionary, or if it is already in the dictionary, it
increments the counter. The "count+1" expression could also be written as
"vocabulary.count". PostgreSQL requires the second form, but SQLite accepts
either.”
https://sqlite.org/lang_upsert.html
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-04-28 15:34:00 | Re: Fwd: SQL transactions executing from VMSS |
| Previous Message | Tom Lane | 2025-04-28 13:54:09 | Re: Upsert error "column reference is ambiguous" |