Tatsuo Ishii <[EMAIL PROTECTED]> 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



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly


Reply via email to