From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | cch(at)cc(dot)kmu(dot)edu(dot)tw |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: [PATCHES] A Patch for MIC to EUC_TW code converting inmbsupport |
Date: | 2000-12-22 08:10:01 |
Message-ID: | 20001222171001Q.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers pgsql-patches |
> > If our application for input is written in PHP (4.0.2)
> > How do we notify PostgreSQL that the frontend encoding
> > is 'BIG5' ? (pg_exec("\encoding BIG5") failed.)
>
> I know there are some patches for supporting \encoding in PHP. Do you
> want to get them?
Sorry for the delay. Here are the patches I promised against PHP
3.0.15 or later.
To set the client encoding to BIG5:
pg_setclientencoding($cid, "BIG5");
($cid is the connection id)
To get the current client encoding:
pg_clientencoding($cid);
Note that these fucntions are already included in the latest PHP4.
--
Tatsuo Ishii
Attachment | Content-Type | Size |
---|---|---|
php.patch.gz | application/octet-stream | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2000-12-22 11:09:54 | RE: RE: SSL Connections [doc PATCH] |
Previous Message | Hannu Krosing | 2000-12-21 20:05:40 | Re: Who is a maintainer of GiST code ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2000-12-22 09:07:50 | RE: Status of JDBC Interface |
Previous Message | Oliver Elphick | 2000-12-22 07:15:28 | Re: (7.1) BIT datatype |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2000-12-22 11:09:54 | RE: RE: SSL Connections [doc PATCH] |
Previous Message | Bruce Momjian | 2000-12-22 03:08:57 | Re: [PATCHES] patch for character set encoding detection for JDBC |