Re: Enum proposal / design

On Thu, Aug 17, 2006 at 08:02:32PM -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > Jim C. Nasby wrote:
> > >> If there was a mechanism to obtain
> > >> field widths from the catalog there would be no need to store the
> > >> field width in each tuple. This would be useful for other types as
> > >> well (UUID and ENUM, for example).
> >
> > > I don't think there is concensus on adding that.
> >
> > Well, it's pie-in-the-sky at the moment because we have no credible
> > design for doing it. Whether any given proposal would get accepted
> > would depend on what its downsides were.
> >
> > Do we (or should we) have a TODO section for "blue sky research
> > ideas"? I'd not object to putting an item like this in such a
> > section. But for most of the TODO items we have a reasonably clear
> > idea of what we're talking about, so this doesn't seem to belong
> > in with the rest.
>
> Blue sky ideas just don't seem natural on the TODO list. Some people
> wanted to use a wiki, and maybe it would be good for that.

I think it would be good to have something, so that people are
occasionally reminded about these things. That's a good way to help
shake ideas out.

Something else to consider is that anything is doable, given enough
effort, which is an argument for just putting it on the TODO.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461