From: | Alexey Dokuchaev <danfe(at)nsu(dot)ru> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Catching unique_violation exception on specific column/index |
Date: | 2018-06-11 10:10:33 |
Message-ID: | 20180611101033.GA40332@regency.nsu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi there,
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.
The usual approach ("EXCEPTION WHEN unique_violation THEN ... END") does
not really cut it because I want to catch unique_violation only when it
happens on "foo_key", and still rightfully complain on others. However,
there is no "EXCEPTION WHEN unique_violation ON (foo_key)" or something.
Is there a way to do this without using triggers and in a less ugly way
than the code below?
IF SQLERRM = 'duplicate key value violates unique constraint' ||
' "foo_key"' THEN
RAISE NOTICE '%: %', SQLSTATE, SQLERRM;
ELSE
RAISE EXCEPTION '%: %', SQLSTATE, SQLERRM;
END IF;
./danfe
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2018-06-11 10:30:13 | Re: Catching unique_violation exception on specific column/index |
Previous Message | Nicolas Seinlet | 2018-06-11 06:47:34 | Re: Sort is generating rows |