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

Re: encoding names

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: <zakkr(at)zf(dot)jcu(dot)cz>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <barry(at)xythos(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: encoding names
Date: 2001-08-22 16:20:50
Message-ID: Pine.LNX.4.30.0108221816160.679-100000@peter.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Tatsuo Ishii writes:

> I don't think you need to change the function name "getdbencoding".
> "get_canonical_database_encoding" is too long anyway.

But getdbencoding isn't semantically different from the old
getdatabaseencoding.  "encoding" isn't the right term anyway, methinks, it
should be "character set".  So maybe database_character_set()?  (No "get"

Peter Eisentraut   peter_e(at)gmx(dot)net

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2001-08-22 16:25:24
Subject: Re: List response time...
Previous:From: Oleg BartunovDate: 2001-08-22 16:17:48
Subject: Re: GiST patches for 7.2 (please apply)

pgsql-patches by date

Next:From: Barry LindDate: 2001-08-22 17:08:02
Subject: Re: encoding names v2.
Previous:From: Liam StewartDate: 2001-08-22 14:59:38
Subject: insert multiple rows attempt two

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