Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> Syntax proposal:
> CREATE CONVERSION <conversion name>
> SOURCE <source encoding name>
> DESTINATION <destination encoding name>
> FROM <conversion function name>
Doesn't a conversion currently require several support functions?
How much overhead will you be adding to funnel them all through
one function?
Basically I'd like to see a spec for the API of the conversion
function...
Also, is there anything in SQL99 that we ought to try to be
compatible with?
regards, tom lane
