(sorry for the delay in responding...)
> You can define user types with spaces in them (note to self: better check
> this), so I don't see why we should hack around it. What do you plan on
> doing with DOUBLE PRECISION and TIME WITH TIMEZONE?
DOUBLE PRECISION is already supported, and becomes float8. TIME WITH
TIMEZONE is currently transparently swallowed to become equivalent to
TIME, for reasons spelled out in the docs. I've toyed with the idea of
implementing the SQL92 version of it, but it is *so* useless and brain
damaged (cf Date et al) that I (at least so far) cannot bring myself
to do so. But if and when, it might be ztime internally.
It is unlikely that we can transparently parse two-word types in
gram.y without explicit support for it. Just adding IDENT IDENT to
simple types leads to a shift/reduce conflict.
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California