pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guido Barosio <gbarosio@gmail.com>
To: Pradeepkumar, Pyatalo (IE10) <Pradeepkumar.Pyatalo@honeywell.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-novice@postgresql.org
Subject: Re: Please help - libpq API
Date: Thu, 8 Sep 2005 11:22:52 +0100
Message-ID: <f7f6b4c705090803222d931d7f@mail.gmail.com> (raw)
In-Reply-To: <77ED2BF75D59D1439F90412CC5B109742415CA8D@ie10-sahara.hiso.honeywell.com>
References: <77ED2BF75D59D1439F90412CC5B109742415CA8D@ie10-sahara.hiso.honeywell.com>

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<http://postgresql.org>page, you will prolly find one
list to suit with this.
or
irc.freenode.net <http://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 !! 
> 
> 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 position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.

view thread (5+ messages)  latest in thread

Message-ID: <f7f6b4c705090803222d931d7f@mail.gmail.com>
Permalink:  ../f7f6b4c705090803222d931d7f@mail.gmail.com/
Also on:    postgresql.org/message-id/f7f6b4c705090803222d931d7f@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: gbarosio@gmail.com, Pradeepkumar.Pyatalo@honeywell.com, pgsql-novice@postgresql.org
  Subject: Re: Please help - libpq API
  In-Reply-To: <f7f6b4c705090803222d931d7f@mail.gmail.com>
  References: <77ED2BF75D59D1439F90412CC5B109742415CA8D@ie10-sahara.hiso.honeywell.com> <f7f6b4c705090803222d931d7f@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox