Re: Null row vs. row of nulls in plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Oleg Serov <serovov(at)gmail(dot)com>
Subject: Re: Null row vs. row of nulls in plpgsql
Date: 2008-09-27 21:00:49
Message-ID: 19114.1222549249@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
> Referring again to my favorite ordinary programming language python, you
> can have a very elegant way of assigning a "record" (a tuple in
> pythonese) to a set of variables and vice versa

There are already perfectly good ways to do that in plpgsql, viz
rowvar := row(x,y,z);
select rowvar.* into x,y,z;

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2008-09-28 01:03:06 Re: Null row vs. row of nulls in plpgsql
Previous Message Hannu Krosing 2008-09-27 20:42:54 Re: Null row vs. row of nulls in plpgsql