On Fri, Aug 24, 2001 at 09:29:06PM +0200, Peter Eisentraut wrote:
> Tatsuo Ishii writes:
>
> > > Maybe we should not touch getdatabaseencoding() right now, given that the
> > > names we currently use are apparently almost correct anyway and
> > > considering the pain it creates to alter them, and instead implement the
> > > information schema views in the future?
> >
> > I thought schema stuffs would be introduced in 7.2 but apparently it
> > would not happen...
>
> True, but right now we'd have to do rather elaborate changes just to
> switch a couple of names to "more correct" versions. Accepting them as
> input is good, but maybe we should hold back on the output part a bit
> until we can do it correctly.
Change output is a very easy work (edit strings in one array). The
important thing is clean internal code for encoding names to faster
and non-duplicated code (use same code for FE and BE).
Well, I prepare it with total back compatible output for all current
routines (pg_char_to_encoding too) and new names will visible by new
routines only (suggested database_character_set(), etc). Right?
Karel
--
Karel Zak <[EMAIL PROTECTED]>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
