Re: Duplicated entries are not ignored even if a "do instead nothing" rule is added.

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Duplicated entries are not ignored even if a "do instead nothing" rule is added.
Date: 2012-01-25 11:52:06
Message-ID: jfoqd6$vqm$3@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2012-01-09, 邓尧 <torshie(at)gmail(dot)com> wrote:

> insert into ACCOUNT(HOME)
> select "v1" as HOME
> where not exists (select 1 from ACCOUNT where HOME =3D "v1")
>
> Surprisingly, I still got the unique constraint violation error, but much
> fewer than before ( only 3 during the last 3 days).
> Any suggestions? Could it be a bug in psycopg2 or postgresql?

No bug, that's ecpected behavior (unless you switch to serializable isolation
level)

when I need to insert if missing and need to avoid all errors I write it like
above but wrap it in a plpgsql function with an exception clause to handle the
error.

--
⚂⚃ 100% natural

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jason Armstrong 2012-01-25 11:54:19 Index on parent/child hierarchy
Previous Message Achilleas Mantzios 2012-01-25 07:52:34 Re: Incomplete startup packet help needed