RE : Record unassigned yet

From: "Johann Robette" <jrobette(at)onyme(dot)com>
To: "'Russell Smith'" <mr-russ(at)pws(dot)com(dot)au>, <pgsql-hackers(at)postgresql(dot)org>
Subject: RE : Record unassigned yet
Date: 2004-10-01 11:28:33
Message-ID: 005f01c4a7a9$c8b80030$a5010a0a@Johann
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Oh sorry about that!
No, I was alright in the syntax. Both are defined as current.
I can't find where the problem lies...

-----Message d'origine-----
De : pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] De la part de Russell Smith
Envoyé : vendredi 1 octobre 2004 13:20
À : pgsql-hackers(at)postgresql(dot)org
Objet : Re: [HACKERS] Record unassigned yet

On Fri, 1 Oct 2004 07:24 pm, Johann Robette wrote:
> Hello,
>
> I'm experiencing a strange problem. Here it is :
> I've created a function with a FOR loop.
>
> DECLARE
> Current RECORD;
> BEGIN
> FOR current IN SELECT * FROM employees LOOP
> Tmp := current.id;
> END LOOP;
> ...
current != Current ?

>
> When I call the function, I get the error :
> ERROR: record " current " is unassigned yet
>
> Any idea?
>
>
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
>

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Huxton 2004-10-01 11:45:54 Re: RE : Record unassigned yet
Previous Message Russell Smith 2004-10-01 11:19:51 Re: Record unassigned yet

Browse pgsql-jdbc by date

  From Date Subject
Next Message Richard Huxton 2004-10-01 11:45:54 Re: RE : Record unassigned yet
Previous Message Russell Smith 2004-10-01 11:19:51 Re: Record unassigned yet