Message-ID: <54BD31F7.3040505@joh.to>
Date: Mon, 19 Jan 2015 17:33:59 +0100
From: Marko Tiikkaja <marko@joh.to>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: PG Docs <pgsql-docs@postgresql.org>
Subject: Re: PL/PgSQL: stmt_fors and variable value after loop
References: <54BD24C1.4060601@joh.to> <26441.1421682246@sss.pgh.pa.us>
 <54BD2E05.2090004@joh.to> <27460.1421684644@sss.pgh.pa.us>
In-Reply-To: <27460.1421684644@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On 1/19/15 5:24 PM, Tom Lane wrote:
> Marko Tiikkaja <marko@joh.to> writes:
>> What I'm doing would look something like this:
>> ...
>> Available workarounds right now would be, as far as I can tell:
>
>>     1) Have separate variables which I assign to inside the loop, and use
>> those in case the loop found exactly one row
>>     2) Aggregate the (currency, balance) pairs into an array first, and
>> decide based on the array's cardinality what to do
>>     3) Use a count(*) OVER () inside the query and EXIT if that count is 1
>>     4) Extract the values back from the sole element in the
>> _AvailableAccounts array
>
>> I don't particularly like any of those.
>
> I would have said that (4) would be the natural thing.  What have you
> got against it?

The balance is in a string meant for human consumption, so I'd have to 
not only dig into the JSON but also extract the relevant portion of that 
string using string manipulation.  Even worse, in the future these 
values might be encrypted, so option #4 isn't even available.


.marko


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs