Re: current is broken - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: current is broken
Date
Msg-id 20000913135646X.t-ishii@sra.co.jp
Whole thread Raw
In response to Re: current is broken  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: current is broken
List pgsql-hackers
> I just fixed one of these in the backend --- looks like someone was
> testing with a C++ compiler instead of an ANSI-C-compliant compiler.
> Need to put the 'int len;' declaration at the top of the function.

Ok.

> > pg_dump.c:268: warning: implicit declaration of function `pg_mbcliplen'
> 
> > Moreover, pg_mbcliplen cannot be used in frontend.
> 
> Ooops.  I guess libpq needs to supply a copy of this function?

Simply copying the function won't work since the way to know what
encoding is used for this session is different between backend and
frontend.

Even better idea would be creating a new function that returns the
actual rule name (after being shorten) from given view name. I don't
think it's a good idea to have codes to get an actual rule name in two
separate places.
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: current is broken
Next
From: Tom Lane
Date:
Subject: Re: current is broken