| From: | Jie Liang <jliang(at)jliang(dot)ipinc(dot)com> |
|---|---|
| To: | Kovacs Zoltan Sandor <tip(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: plpgsql |
| Date: | 2000-12-12 18:14:32 |
| Message-ID: | Pine.BSF.4.21.0012121010050.25634-100000@jliang.ipinc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
OO,
That's a big disadvantage, because if the table is huge, using select stmt
walking even on an index will take some time and duplicate occur not
often, efficiency is a big problem.
Thanks anyway.
Jie LIANG
Internet Products Inc.
10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873
jliang(at)ipinc(dot)com
www.ipinc.com
On Tue, 12 Dec 2000, Kovacs Zoltan Sandor wrote:
> > Hi, there,
> >
> > Is there any way to handle exception ( such as cannot insert duplicate key on
> > a unique index) in
> > plpgsql function?
> >
> > I don't want it abort whole transaction instead I want to do something else if
> > it happened,
> > but I don't want to use a select stmt first to waste the time.
> Bad news: there is no such statement in PLPGSQL you like. My usual way to
> do this is the same you wrote (SELECT first, if no rows FOUND, do the
> INSERT).
>
> Zoltan
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jie Liang | 2000-12-12 18:36:03 | Re: Foreign key constraint |
| Previous Message | Mike Castle | 2000-12-12 16:56:28 | Re: plpgsql |