Skip site navigation (1) Skip section navigation (2)

Re: cursors in postgres

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: pgsql-general general <pgsql-general(at)postgresql(dot)org>
Subject: Re: cursors in postgres
Date: 2007-03-29 15:08:35
Message-ID: 198B5B3B-574E-4AC8-839E-944EE83F3B0A@themactionfaction.com (view raw or flat)
Thread:
Lists: pgsql-general
On Mar 29, 2007, at 10:47 , Jasbinder Singh Bali wrote:

> Hi,
> I've written a function using cursors as follows:
> can anyone please comment on the text in red.
>
>
> ------------------------------------------------------
>
> CREATE OR REPLACE FUNCTION sp_insert_tbl_email_address(int4, text,  
> text, text)
>   RETURNS void AS
> $BODY$
>     DECLARE
>     uid int4 ;
>     src text;
>     local text;
>     domain text;
>     cur_dup_check CURSOR FOR SELECT * FROM tbl_email_address
>     WHERE unmask_id=$1 and source=$2 and email_local=$3 and  
> email_domain=$4;
>
>
> BEGIN
>
>     OPEN cur_dup_check ;
>
>     FETCH cur_dup_check INTO uid,src,local,domain;
>  --need to check the fetch status of the cursor whether any rows  
> were returned or not and keep moving to the next record till fetch  
> status is not zero

Huh? Why don't you simply declare a unique constraint across the  
columns you require?

-M

In response to

pgsql-general by date

Next:From: Jasbinder Singh BaliDate: 2007-03-29 15:11:47
Subject: Re: cursors in postgres
Previous:From: Filip RembiaƂkowskiDate: 2007-03-29 15:03:44
Subject: Re: cursors in postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group