| From: | Alexey Dokuchaev <danfe(at)nsu(dot)ru> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Catching unique_violation exception on specific column/index |
| Date: | 2018-06-11 10:58:34 |
| Message-ID: | 20180611105834.GA47390@regency.nsu.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 11, 2018 at 12:30:13PM +0200, Thomas Kellerer wrote:
> Alexey Dokuchaev schrieb am 11.06.2018 um 12:10:
> > I have a table with several UNIQUE and CHECK constraints. One of these
> > UNIQUE constraints actually *can* be violated -- not on the table level,
> > of course, but on the application level -- meaning, if the entry with
> > particular foo_key is already in there, do not throw an exception, just
> > silently do nothing.
>
> What's wrong with:
>
> INSERT ...
> ON CONFLICT (foo_key) DO NOTHING
Nothing I guess, except that it is available since 9.5 (right?), and I try
to stay compatible with 9.3. Sorry for not saying this in the first place.
./danfe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-06-11 11:26:16 | Re: Catching unique_violation exception on specific column/index |
| Previous Message | Andreas Kretschmer | 2018-06-11 10:54:22 | Re: Catching unique_violation exception on specific column/index |