Re: handling duplicate row exception
От
Filip Rembiałkowski
Тема
Re: handling duplicate row exception
Дата
Msg-id
CAP_rwwkHqUHmK3rYL3hvH2=R6MPbapqyuTtOi923GnULjRfZCw@mail.gmail.com
Ответ на
handling duplicate row exception (Amar Dhole)
Список
Дерево обсуждения
Combining several CTEs with a recursive CTE Thomas Kellerer <spam_eater@gmx.net>
Re: Combining several CTEs with a recursive CTE David Johnston <polobo@yahoo.com>
Re: Combining several CTEs with a recursive CTE Thomas Kellerer <spam_eater@gmx.net>
handling duplicate row exception Amar Dhole <adhole@tibco.com>
Re: handling duplicate row exception Filip Rembiałkowski <plk.zuber@gmail.com>
Re: handling duplicate row exception Amar Dhole <adhole@tibco.com>
Re: handling duplicate row exception Filip Rembiałkowski <plk.zuber@gmail.com>
Hi
There is no IGNORE_DUP_KEY equivalent in PostgreSQL.
If you are 100% sure that you want to ignore unique key violations, you can wrap your INSERT code in PL/PgSQL block and handle the exception yourself.
I mean:
DO $$
BEGIN
INSERT INTO foo (bar,baz) SELECT 42, 666;
EXCEPTION WHEN unique_violation THEN RAISE NOTICE 'row skipped';
END;
$$
BTW - which version of PostgreSQL are you using?
Filip
There is no IGNORE_DUP_KEY equivalent in PostgreSQL.
If you are 100% sure that you want to ignore unique key violations, you can wrap your INSERT code in PL/PgSQL block and handle the exception yourself.
I mean:
DO $$
BEGIN
INSERT INTO foo (bar,baz) SELECT 42, 666;
EXCEPTION WHEN unique_violation THEN RAISE NOTICE 'row skipped';
END;
$$
BTW - which version of PostgreSQL are you using?
Filip
2011/9/21 Amar Dhole <adhole@tibco.com>
Hi All,
I have a requirement where my application tries to enter the duplicate row in table using batchexceute code. And batch exception is thrown we checked error code and skip it but after this exception all my next update/insert gets error out with following exception
"Database error. SQL state 25P02. Database specific error code (if any) was 0. Database error message (if any) was: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block.:
Is there any way to proceed ahead like in sql server we have options while creating table IGNORE_DUP_KEY = ON if this is set warning is generated instead of Exception so the other insert/update can proceed ahead.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
В списке pgsql-sql по дате отправления
