Skip site navigation (1) Skip section navigation (2)

Re: ecpg is broken in current

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: meskes(at)postgresql(dot)org
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ecpg is broken in current
Date: 2000-09-27 01:44:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> 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


pgsql-hackers by date

Next:From: James CribbDate: 2000-09-27 02:10:23
Subject: \l+ dumps core
Previous:From: Tatsuo IshiiDate: 2000-09-27 01:26:44
Subject: Re: \l+ dumps core

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group