Function Issue! - Mailing list pgsql-sql

From Theo Galanakis
Subject Function Issue!
Date
Msg-id 82E30406384FFB44AFD1012BAB230B55037D051E@shiva.au.lpint.net
Whole thread Raw
Responses Re: Function Issue!
List pgsql-sql
<p><font face="Arial" size="2">Can anyone tell me what is wrong with the function below ? </font><br /><font
face="Arial"size="2">It throws an ERROR:  syntax error at or near "FETCH" at character 551</font><p><font face="Arial"
size="2">CREATEOR REPLACE FUNCTION "public"."theo_test2" () RETURNS OPAQUE AS'</font><br /><font face="Arial"
size="2">BEGIN</font><br/><font face="Arial" size="2">   declare curr_theo cursor for select * from
node_names;</font><br/><font face="Arial" size="2">   fetch next from curr_theo;</font><br /><font face="Arial"
size="2">  close curr_theo;</font><br /><font face="Arial" size="2">END;</font><br /><font face="Arial"
size="2">'LANGUAGE'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY DEFINER;</font><br /><p><font face="Arial"
size="2">However,this appears to work :</font><br /><font face="Arial" size="2">begin;</font><br /><font face="Arial"
size="2"> declarecurr_theo cursor for select * from node_names;</font><br /><font face="Arial" size="2"> fetch next
fromcurr_theo;</font><br /><font face="Arial" size="2"> close curr_theo;</font><br /><font face="Arial"
size="2">end;</font><table><tr><tdbgcolor="#ffffff"><font
color="#000000">______________________________________________________________________<br/>This email, including
attachments,is intended only for the addressee<br />and may be confidential, privileged and subject to copyright. If
you<br/>have received this email in error, please advise the sender and delete<br />it. If you are not the intended
recipientof this email, you must not<br />use, copy or disclose its content to anyone. You must not copy or <br
/>communicateto others content that is confidential or subject to <br />copyright, unless you have the consent of the
contentowner.<br /></font></td></tr></table> 

pgsql-sql by date:

Previous
From: Jan Wieck
Date:
Subject: Re: multi column foreign key for implicitly unique columns
Next
From: Tom Lane
Date:
Subject: Re: Function Issue!