X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DEAE0D8673 for ; Thu, 8 Sep 2005 07:22:55 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 46804-07 for ; Thu, 8 Sep 2005 10:22:50 +0000 (GMT) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.192]) by svr1.postgresql.org (Postfix) with ESMTP id 5F392D8634 for ; Thu, 8 Sep 2005 07:22:50 -0300 (ADT) Received: by nproxy.gmail.com with SMTP id c2so289692nfe for ; Thu, 08 Sep 2005 03:22:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=gDykfT0xGC2gZDNyhOgE+Tyj0n8J+NKCaY/d8x5kpWnLB8So6lG0Uc+CQzCcobNEZsMqGJa0jIRjo4v4dfvK4ePQaOMFQsW0xIwNRfYEAlSRCOgBkvb+0zWVDWZ9HirzDQRH9y6EHPxSRbiaHRmcq4LEkx2/IVJ0BpDbtyXoM0k= Received: by 10.48.250.9 with SMTP id x9mr224441nfh; Thu, 08 Sep 2005 03:22:52 -0700 (PDT) Received: by 10.48.250.10 with HTTP; Thu, 8 Sep 2005 03:22:52 -0700 (PDT) Message-ID: Date: Thu, 8 Sep 2005 11:22:52 +0100 From: Guido Barosio Reply-To: gbarosio@gmail.com To: "Pradeepkumar, Pyatalo (IE10)" Subject: Re: Please help - libpq API Cc: pgsql-admin@postgresql.org, pgsql-novice@postgresql.org In-Reply-To: <77ED2BF75D59D1439F90412CC5B109742415CA8D@ie10-sahara.hiso.honeywell.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20273_24753817.1126174972610" References: <77ED2BF75D59D1439F90412CC5B109742415CA8D@ie10-sahara.hiso.honeywell.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.167 required=5 tests=[AWL=0.086, HTML_30_40=0.056, HTML_MESSAGE=0.001, RCVD_BY_IP=0.024] X-Spam-Level: X-Archive-Number: 200509/73 X-Sequence-Number: 18810 ------=_Part_20273_24753817.1126174972610 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I think that this is the wrong list for your problem. My suggestions: contact pgsql-hackers or check the lists in the postgresql.orgpage, you will prolly find one list to suit with this. or irc.freenode.net , join #postgresql . Good boys=20 lurking there, you will have to fight, but help will be given if you have= =20 good maners and offer a pizza. Good luck. G.- On 9/8/05, Pradeepkumar, Pyatalo (IE10) =20 wrote: >=20 >=20 > Hi all,=20 >=20 > I have already posted my query regarding libpq functions and wide=20 > character support. Pls somebody help me. I am using libpq API functions i= n=20 > my C code to do operations on the database. But the problem I m facing is= =20 > API functions like PQexec() etc....accept only char * .... but as part of= =20 > localization, the queries I want to executed contain chinese characters= =20 > which are multibytes. So the queries I want to execute are in wchar_t *= =20 > format and PQ exec() accepts only char *. Is there any alternate way to= =20 > execute queries having wide characters.=20 >=20 > Even if somehow if I convert wchar_t * to char * and provide it to=20 > Postgres, how will it differentiate between chinese characters and normal= =20 > characters ?? >=20 > Please help !!=20 >=20 > Regs,=20 > Pradeep=20 >=20 >=20 > This e-mail and any attachments thereto, are intended only for use=20 > by the addressee(s) named herein and contain Honeywell confidential=20 > information. If you are not the intended recipient of this e-mail, you= are=20 > hereby notified that any dissemination, distribution or copying which= =20 > amounts to misappropriation of this e-mail and any attachments thereto= , is=20 > strictly prohibited. If you have received this e-mail in error, please= =20 > immediately notify me and permanently delete the original and any copy= of=20 > any e-mail and any printout thereof."=20 > =20 > =20 >=20 --=20 "Adopting the position that you are smarter than an automatic optimization algorithm is generally a good way to achieve less performance, not more" - Tom Lane. ------=_Part_20273_24753817.1126174972610 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

I think that this is the wrong list for your problem. My suggestions:

contact pgsql-hackers or check the lists in the postgresql.org page, you will prolly find one list to suit with = this.
or
irc.freenode.net, join #postgresql = . Good boys lurking there, you will have to fight, but help will be given if you have good maners and offer a pizza.

Good luck.

G.-

On 9/8/05, Pradeepkumar, Pyatalo (IE10) <Pradeepkumar.Pyatalo@honeywell.com> wrote:=

Hi all,

I have already posted my query regarding libpq functions and wide character support. Pls somebody help me. I am using libpq API functions in my C code to do operations on the database. But the problem I m facing is API functions like PQexec() etc....accept only char * .... but as part of localization, the queries I want to executed contain chinese characters which are multibytes. So the queries I want to execute are in wchar_t * format and PQ exec() accepts only char *. Is there any alternate way to execute queries having wide characters.

Even if somehow if I convert wchar_t *  to char * and provide it to Postgres, how will it differentiate between chinese characters and normal characters ??

Please help !!<= /font>

Regs,
Pradeep


    This e-mail and any attachments thereto, are intended only for use by the addressee(s) named herein and contain Honeywell confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying which amounts to misappropriation of this e-mail and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof."





--
"Adopting the posi= tion that you are smarter than an automatic
optimization algorithm is ge= nerally a good way to achieve less
performance, not more" - Tom Lan= e. ------=_Part_20273_24753817.1126174972610--