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

Re: What's wrong in this pltcl function ?

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Constantin Teodorescu <teo(at)flex(dot)ro>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: What's wrong in this pltcl function ?
Date: 2002-10-14 14:11:27
Message-ID: Pine.LNX.4.21.0210141506580.584-100000@ponder.fairway2k.co.uk (view raw or flat)
Thread:
Lists: pgsql-interfaces
On Mon, 14 Oct 2002, Constantin Teodorescu wrote:

> create function ruldeb(bpchar) returns bpchar as '
>     set cont $1
>     set rulaj 0.0
>     spi_exec -array rec "select valoare from valori where debitor LIKE 
> \'$cont%\'" {
>         set rulaj [expr {$rulaj + $rec(valoare)}]
>     }
>     if {![info exists GD(conturi_lookup)]} {
>         set GD(conturi_lookup) [spi_prepare "select cheie,denumire from 
> conturi where id=\'\\$1\'" [list bpchar]]
>     }
>     spi_execp -count 1 $GD(conturi_lookup) [list $cont]
>     return "{$cheie} {$denumire} $rulaj"
> ' LANGUAGE 'pltcl';
> 
> 
> is giving the following error:
> 
> ERROR:  pltcl: can't read "cheie": no such variable
> can't read "cheie": no such variable
>     while executing
> "return "{$cheie} {$denumire} $rulaj""
>     (procedure "__PLTcl_proc_1759991" line 12)
>     invoked from within
> "__PLTcl_proc_1759991 4:0:1:1:2:"


Looks like your prepared query is not finding any matching tuples.

If a query returns 0 tuples then all column variables will be undefined.
Undefined because if you set them before then they will not be unset. This
differs from the case where a tuple has been returned by the query but a
column's value is NULL. In this case the TCL variable is unset.


-- 
Nigel J. Andrews


In response to

pgsql-interfaces by date

Next:From: Constantin TeodorescuDate: 2002-10-14 14:19:29
Subject: Re: What's wrong in this pltcl function?
Previous:From: Constantin TeodorescuDate: 2002-10-14 09:14:03
Subject: What's wrong in this pltcl function ?

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