Re: encoding: ODBC, createdb
От | Karel Zak |
---|---|
Тема | Re: encoding: ODBC, createdb |
Дата | |
Msg-id | 20010821093744.B21816@zf.jcu.cz обсуждение исходный текст |
Ответ на | Re: encoding: ODBC, createdb (Hiroshi Inoue <Inoue@tpf.co.jp>) |
Список | pgsql-hackers |
On Tue, Aug 21, 2001 at 10:00:21AM +0900, Hiroshi Inoue wrote: > Karel Zak wrote: > > > > I found some other things: > > > > - ODBC -- here is some multibyte stuff too. Why ODBC code don't use > > pg_wchar.h where is all defined? In odbc/multibyte.h is again defined > > all encoding identificators. > > > > IMHO we can use for ODBC same solution as for libpq and compile it > > with encname.c file too. > > ODBC under Windows needs no source/header files in PostgreSQL > other than in src/interfaces/odbc. It's not preferable for > psqlodbc driver to be sensitive about other PostgreSQL changes > because the driver has to be able to talk multiple versions of > PostgreSQL servers. In fact the current driver could talk to > any server whose version >= 6.2(according to a person). > As for pg_wchar.h I'm not sure if it could be an exception > and we could expect for the maintainer to take care of ODBC. > If I were he, I would hate it. In the odbc/multibyte.h is if (strstr(str, "%27SJIS%27") || strstr(str, "'SJIS'") || strstr(str, "'sjis'")) ..and same line for BIG5 I add here new names 'Shift_JIS' and 'Big5' only. Karel -- Karel Zak <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
В списке pgsql-hackers по дате отправления: