Re: Behaviour of rows containg not-null domains in plpgsql - Mailing list pgsql-hackers

From Florian G. Pflug
Subject Re: Behaviour of rows containg not-null domains in plpgsql
Date
Msg-id 47C1C4AE.8020409@phlo.org
Whole thread Raw
In response to Re: Behaviour of rows containg not-null domains in plpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Florian G. Pflug" <fgp@phlo.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Behaviour of rows containg not-null domains in plpgsql
Next
From: Simon Riggs
Date:
Subject: Re: Batch update of indexes on data loading