Re: plpgsql
От | Jie Liang |
---|---|
Тема | Re: plpgsql |
Дата | |
Msg-id | Pine.BSF.4.21.0012121010050.25634-100000@jliang.ipinc.com обсуждение исходный текст |
Ответ на | Re: plpgsql (Kovacs Zoltan Sandor <tip@pc10.radnoti-szeged.sulinet.hu>) |
Список | 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@ipinc.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 >
В списке pgsql-sql по дате отправления: