Re: encoding: ODBC, createdb - Mailing list pgsql-hackers

From Karel Zak
Subject Re: encoding: ODBC, createdb
Date
Msg-id 20010908100155.A6888@zf.jcu.cz
Whole thread Raw
In response to Re: encoding: ODBC, createdb  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Fri, Sep 07, 2001 at 04:11:25PM -0400, Bruce Momjian wrote:
> 
> Was this completed?
> 
> > 
> >  I found some other things:
> > 
> > - why database encoding for new DB check 'createdb' script and not
> >   CREATE DATABASE statement? (means client only encodings, like BIG5)?
It was include in my large multibyte patch and it's complete in
dbcommands.c (It was non-reported bug in previous releases). 

> > - 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. 
Probably done, it check ODBC maintainer.
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 by date:

Previous
From: Karel Zak
Date:
Subject: Re: CURRENT CVS: MULTIBYTE: CANT CONNECT....
Next
From: Karel Zak
Date:
Subject: Re: CURRENT CVS: MULTIBYTE: CANT CONNECT....