| From: | Dane Foster <studdugie(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: A question about PL/pgSQL DECLAREd variable behavior |
| Date: | 2015-10-22 21:27:52 |
| Message-ID: | CA+WxinJNbR6Pg_yJuJLvntJRkv9r8XYrDKhxEg2OwuuP_TdDSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 22, 2015 at 2:00 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 10/21/15 9:32 PM, Dane Foster wrote:
>
>> "If STRICT is not specified in the INTO clause, then target will be
>> set to the first row returned by the query, or to nulls if the query
>> returned no rows."
>>
>> Foot removed from mouth.
>>
>
> Note however that there's some unexpected things when checking whether a
> record variable IS (NOT) NULL. It's not as simple as 'has the variable been
> set or not'.
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>
Please elaborate. I'm entirely new to PL/pgSQL so the more details you
can provide the better.
Thanks,
Dane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Vanasco | 2015-10-22 22:22:51 | Re: temporary indexes? |
| Previous Message | Jim Nasby | 2015-10-22 21:04:13 | Re: temporary indexes? |