From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | James Sharrett <jsharrett(at)tidemark(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: dynamically referencing a column name in a function |
Date: | 2014-02-15 23:29:39 |
Message-ID: | 52FFF863.5060508@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 02/15/2014 02:41 PM, James Sharrett wrote:
> Thanks Adrian. The problem is that the data query will return many
> columns all of which I need in later operations. For this specific block
> in the process, I need to take a pair of columns, based on user inputs,
> and run their values them thru the operations performed in the sub
> function to perform some operations and return the results and I need the
> values I pass into the parameter to be in sync with the recordset which
> will have many records with the same values for the column pairs so
> keeping the whole record being operated on in line with the values passed
> to the sub-function becomes the difficult part. I¹m trying to avoid using
> a cursor but even with that I think I may run into similar issues.
>
Well I did say it probably would not scale:) Without a concrete example
of the actual process it would be hard to offer any specific advice.
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | amul sul | 2014-02-17 05:52:48 | Trigger SQL script execution after DROP EXTENSION |
Previous Message | James Sharrett | 2014-02-15 22:41:50 | Re: dynamically referencing a column name in a function |