Re: ecpg is broken in current

From: Christof Petig <christof(dot)petig(at)wtal(dot)de>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: meskes(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ecpg is broken in current
Date: 2000-09-29 17:04:06
Message-ID: 39D4CB86.35D704FC@wtal.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii wrote:

> > On Fri, Sep 22, 2000 at 03:31:59PM +0900, Tatsuo Ishii wrote:
> > > pgc.o(.text+0x582): undefined reference to `pg_mbcliplen'
> > > pgc.o(.text+0x953): undefined reference to `pg_mbcliplen'
> > > ...
> > > pg_mbcliplen cannot be used in the frontend. Remove them, please.
> >
> > Is there any way to use a similar functionality in ecpg? I don't like to run
> > truncate the text too early.
>
> To truncate a mulbyte characters properly, you need to know what
> encoding is used for a .pgc file that ecpg about to process. Currently
> there is no mechanism in ecpg (and all other frontend) to know what
> encoding is used for the .pgc files. This is a tough problem...
> --
> Tatsuo Ishii

I would recommend a command line option overriding an environment variable
(fallback). Isn't there some LC_* indicating the default encoding.
But on the other hand, compiling would most likely take place in 'C'.

Christof

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-09-29 17:04:36 Re: Database log
Previous Message Jean-Christophe Pazzaglia 2000-09-29 16:44:08 Database log