On Wed, 21 Feb 2001, Tatsuo Ishii wrote:
> Please understand there is no standard for charset/encoding names in
> SQL92/99 itself. The SQL standard just says "you can import any
> charset/encoding from anywhere if you can". Please correct me if I am
> wrong.
In SQL standards not, but all probably known for example ISO names or
some form for this.
> However, I do not object to change encoding names if there are enough
> agrees (and as long as the backward compatibilities are kept).
You not must change current names, you can add to pg_conv_tbl[] new lines
with names synonym for already existing encoding.
An example:
{LATIN1, "LATIN1", 0, latin12mic, mic2latin1, 0, 0}, {LATIN1, "ISO-8859-1", 0, latin12mic, mic2latin1, 0, 0},
And if you order this table by alphabet and in pg_char_to_encoding()
you use Knuth's binary search intead current seq. scannig by for() every
thing will faster and more nice. It's easy.
What? :-)
Karel
