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

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

> Is there some difficulty in implementing row-type defaults, or is it
> just that nobody cared enough about them to do the work?

The second statement is certainly true, I don't know about the first.
Feel free to take a shot at it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Behaviour of rows containg not-null domains in plpgsql
Next
From: "Florian G. Pflug"
Date:
Subject: Re: Behaviour of rows containg not-null domains in plpgsql