Subject: Re: Handling (None,) Query Results
To: hagen@datasundae.com, psycopg@lists.postgresql.org, psycopg@postgresql.org
References: <5f75fbb2-6da2-60f3-5488-9013d1328361@datasundae.com>
 <80505104-1778-6157-cb9f-8cbafb748660@aklaver.com>
 <067801d6cb21$c6b442f0$541cc8d0$@datasundae.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
Message-ID: <63e5c526-7e07-ad4b-f891-ac5272257507@aklaver.com>
Date: Sat, 5 Dec 2020 08:19:32 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <067801d6cb21$c6b442f0$541cc8d0$@datasundae.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 12/5/20 8:14 AM, hagen@datasundae.com wrote:
> I tried  the COALESCE approach but I thought the query still returned (None,).

 From docs:

https://www.postgresql.org/docs/12/functions-conditional.html#FUNCTIONS-COALESCE-NVL-IFNULL

"The COALESCE function returns the first of its arguments that is not 
null. Null is returned only if all arguments are null. ..."

So if it returned NULL/None then the first and second values both 
resolved to NULL.

> 
> However, I just tried it again and I got a (Decimal('0'),) return.
> 
> I should be able to make that work.
> 
> Thanks everyone for your rapid assistance.
> 
> Best,
> 
> Hagen
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com