Re: effective SELECT from child tables - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: effective SELECT from child tables
Date
Msg-id 20051002210528.GL30492@svana.org
Whole thread Raw
In response to Re: effective SELECT from child tables  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: effective SELECT from child tables
List pgsql-hackers
On Sun, Oct 02, 2005 at 11:51:27PM +0300, Hannu Krosing wrote:
> Right. Actually the "default" value returned for missing columns should
> be different from the default for new values and should be settable only
> once, when adding the column, else issues would become really really
> weird.

Right, the only way I could really imagine it working is have a flag,
attautodefault which if set would return the default instead of NULL.
It would only ever be set if the ADD COLUMN SET DEFAULT happened
together. But does this mean you have one magic default fixed for the
life of the column and the actual default which can be changed anytime?
Seems messy, though possible...

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

pgsql-hackers by date:

Previous
From: mark@mark.mielke.cc
Date:
Subject: Re: effective SELECT from child tables
Next
From: Hannu Krosing
Date:
Subject: Re: effective SELECT from child tables