"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> I just stumbled over the following behaviour, introduced with 8.3, and
> wondered if this is by design or an oversight.
No, this was in 8.2.
> If you define a domain over some existing type, constrain it to
> non-null values, and use that domain as a field type in a table
> definition, it seems to be impossible to declare pl/pgsql variables
> of that table's row type. The problem seems to be that upon declaration,
> the row variable is filled with nulls - but since the domain is marked
> not-null, that immediatly triggers an exception.
What else would you expect it to do? AFAICS any other behavior would be
contrary to spec.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Andy Pavlo||Date: 2008-02-24 18:04:42|
|Subject: Re: Improved (De)Serialization Support|
|Previous:||From: Joshua D. Drake||Date: 2008-02-24 17:47:15|
|Subject: Re: 8.3 / 8.2.6 restore comparison|