Re: error handling unique key constraint in pgsql

From: Dinesh <dbhandary(at)mongonet(dot)net>
To: Alex Hunsaker <badalex(at)gmail(dot)com>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: error handling unique key constraint in pgsql
Date: 2008-06-10 21:54:55
Message-ID: 484EF82F.8080500@mongonet.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Great. That's what I was looking for. Thanks a lot guys.

Dinesh

Alex Hunsaker wrote:
> On Tue, Jun 10, 2008 at 2:46 PM, Dinesh <dbhandary(at)mongonet(dot)net> wrote:
>
>> Hi Scott,
>>
>> Thanks for your reply.
>>
>> Is there a built in exception in pl/pgsql ( similar to oracle's
>> |DUP_VAL_ON_INDEX ) that I can use?
>>
>> I ran into an unique situation a couple of days ago. Procedure that inserts
>> a new value into unique index column was called at the same time. I even
>> check if the value exist before inserting, but one of the instance of the
>> function gave me an unique constraint violation error.
>>
>> My code looks like this:
>>
>> select into var * from table;
>>
>> if not found then
>> insert into table
>> values (a);
>> end if;
>> |
>> I would imagine the postgres db would inherently handle situation like this,
>> but it did not.
>>
>> Thanks.
>>
>
>
> See http://www.postgresql.org/docs/8.3/static/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING,
> specifically example Example 38-1.
>
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Igniris Valdivia Baez 2008-06-10 23:07:59 I want to delete mi account in the mail list
Previous Message Alex Hunsaker 2008-06-10 21:38:50 Re: error handling unique key constraint in pgsql