Re: DEFAULT of domain ignored in plpgsql (8.4.1)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DEFAULT of domain ignored in plpgsql (8.4.1)
Date: 2009-11-21 15:52:14
Message-ID: 14855.1258818734@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> (2) this change, while very useful, does change what had been a simple
> rule ("All variables are NULL unless specifically set otherwise") into a
> conditional one ("All variables are NULL unless set otherwise OR unless
> they are declared as domain types with defaults"). Do people feel that
> the new behavior would be sufficiently intuitive to avoid user confusion?

I'm inclined to leave it alone. It complicates the mental model, and
frankly attaching defaults to domains was not one of the SQL committee's
better ideas anyway. It's *fundamentally* non-orthogonal.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2009-11-21 16:27:16 Re: DEFAULT of domain ignored in plpgsql (8.4.1)
Previous Message Tom Lane 2009-11-21 15:48:59 Re: Proposal: USING clause for DO statement