Thomas Lockhart writes:
> I'm not sure that I agree that multi-word character types are required
> internally. Somehow that seems to just push the problem of
> SQL92-specific syntax to another part of the code. We could just as
> easily (?) translate *every* "xxx VARYING" to "varxxx" on input, and
> do the inverse on output or pg_dump.
On the one hand I propose what seems like editing a handful of lines in
the bootstrap scanner (an internal interface) to solve this problem once
and for all. What you are proposing is that every client interface (libpq,
SPI, PL du jour, who knows) will have to know a list of the latest hacks
of type conversions in the backend. And it would be very confusing to
people defining user types like "varxxx".
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?
Confused ...
--
Peter Eisentraut Sernanders väg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden