Re: plpgsql variable trouble - Mailing list pgsql-general

From Tom Lane
Subject Re: plpgsql variable trouble
Date
Msg-id 4824.975598330@sss.pgh.pa.us
Whole thread Raw
In response to plpgsql variable trouble  (Phil Steinke <lintec@engsoc.queensu.ca>)
List pgsql-general
Phil Steinke <lintec@engsoc.queensu.ca> writes:
> The problem with my code seems to be that the "given_field" variable isn't
> being interpolated in the assignment statement.

plpgsql is not a string-substitution language; you cannot expect the
value of a variable to be used as a table or field name in a query.
This is true because plpgsql precompiles queries into query plans
and saves the plans for repeated execution.  That's a win for speed
but costs flexibility.

You *can* get that sort of result in pltcl or plperl, which don't do
any fancy caching.  You just form the query as a string value using the
usual expression evaluation rules of those languages, and that string
gets submitted to the SQL parser and query engine.  Less speed, more
flexibility.

I believe 7.1's plpgsql will have an EXECUTE <string> command that lets
you get the second effect in plpgsql too.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: backup and store oids
Next
From: Doug Semig
Date:
Subject: Re: Database cluster?