Samofatov, Nickolay wrote:

>>
>>Engine should be able to load charsets with only charset name.
>
>
> Why?
>

See below.

>
>>This is necessary to open a database when the client is
>>connecting with a charset different from the server OS
>>charset/codepage.
>

A example:

Here native Windows charset is WIN1252. DOS (cmd prompt) use DOS850.

isql -ch dos850
SQL> create database 'á.fdb';

Currently, this create wrong filename in the server.

If engine can load DOS850 charset before create 'á.fdb' it can convert the filename to native Windows charset (WIN1252).

This is not very important, but why not do things right?

>
>>And SQL 2003 remove ability to specify external file in
>>CREATE COLLATION.
>
>
> CREATE COLLATION definition of SQL 2003 is skeletal. My understanding is
> that we are supposed to extend it the ways we wish.

Ok. But the thing was removed from the standard. It exist in SQL-99 but not in SQL-2003.
Maybe someone see that this is not nice.


Adriano