RE : Record unassigned yet
От | Johann Robette |
---|---|
Тема | RE : Record unassigned yet |
Дата | |
Msg-id | 005f01c4a7a9$c8b80030$a5010a0a@Johann обсуждение исходный текст |
Ответ на | Re: Record unassigned yet (Russell Smith <mr-russ@pws.com.au>) |
Ответы |
Re: RE : Record unassigned yet
|
Список | pgsql-hackers |
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@postgresql.org [mailto:pgsql-hackers-owner@postgresql.org] De la part de Russell Smith Envoyé : vendredi 1 octobre 2004 13:20 À : pgsql-hackers@postgresql.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
В списке pgsql-hackers по дате отправления: