Re: Behaviour of rows containg not-null domains in plpgsql

From: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Behaviour of rows containg not-null domains in plpgsql
Date: 2008-02-24 19:25:34
Message-ID: 47C1C4AE.8020409@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
>> Plus, the fact that we don't support "default" specifications in
>> pl/pgsql for row types turns this inconvenience into a major PITA,
>
> You mean initialization expressions, not defaults, correct? (I would
> consider the latter to mean that whatever attrdef entries were attached
> to the rowtype's parent table would be used implicitly.)
Yeah, I mean writing "declare; v_var schema.table default row(....)"

regards, Florian Pflug

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Mielke 2008-02-24 21:21:27 insert ... delete ... returning ... ?
Previous Message Tom Lane 2008-02-24 19:16:13 Re: Behaviour of rows containg not-null domains in plpgsql