SQL99 allows on the fly encoding conversion:
CONVERT('aaa' USING myconv 'bbb')
So there could be more than 1 conversion for a paticlular encodings
pair. This lead to an ambiguity for "default" conversion used for the
frontend/backend automatic encoding conversion. Can we add a flag
indicating that this is the "default" conversion? The new proposed
syntax would be:
CREATE CONVERSION <conversion name> FOR <source encoding name> TO <destination encoding name> FROM
<conversionfunction name> [DEFAULT]
Comments?
--
Tatsuo Ishii