Kris Jurka wrote:
>
> On Sun, 19 Sep 2004, Oliver Jowett wrote:
>
>
>>8.0 backends report the server_encoding value of the database via
>>ParameterStatus during startup. I'd like to use this to detect SQL_ASCII
>>databases and complain loudly.
>
>
> That would certainly help people who have setup their databases
> incorrectly, but it is actually legal to have a setup like this as long as
> you only use seven bit ascii characters.
We could support this case by requiring charSet=SQL_ASCII to be
specified if you have this case. (this would set client_encoding =
SQL_ASCII and interpret data as US-ASCII).
Part of the problem is that SQL_ASCII seems to mean "just store whatever
I'm given directly"; there is no real "7-bit ascii only" encoding?
> I'm not sure where I stand on
> this. There are probably plenty of databases that are working fine with
> the current setup. For example even using 8 bit chars in a SQL_ASCII
> database, if all clients are unicode then the only problem you'll see is
> the length check in something like varchar(100) failing.
We could support this with charSet=UNICODE (set client_encoding =
SQL_ASCII and interpret data as UTF-8)
-O
