I'm inclined to accept this for beta 3. Although it seems like a new
feature, the inability to set PGCLIENTENCODING where it may be
required could be considered a bug.
Thoughts?
On Mon, Jun 7, 2010 at 4:43 PM, Hiroshi Saito <z-saito@guitar.ocn.ne.jp> wrote:
> Ooops, this:-)
>
> ----- Original Message ----- From: "Dave Page" <dpage@pgadmin.org>
>
>
>> Show us the patch man!!
>>
>> :-)
>>
>> On Mon, Jun 7, 2010 at 4:28 PM, Hiroshi Saito <z-saito@guitar.ocn.ne.jp>
>> wrote:
>>>
>>> Hi.
>>>
>>> I need setenv for plugins. Because, there must not be client_encoding in
>>> Japan.
>>> It does not function now.
>>> The following specifications are considered. Environment -
>>> VARIABLE=VALUE[,VARIABLE=VALUE]
>>> example)
>>> Environment=PGCLIENTENCODING=SJIS,OTHERS_ENV=VAL
>>>
>>> It is important to have a function, though a user has to setup myself.
>>> Does someone any objection?
>>>
>>> Regards,
>>> Hiroshi Saito
>>>
>>>
>>>
>>>
>>> --
>>> Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgadmin-hackers
>>>
>>
>>
>>
>> --
>> Dave Page
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise Postgres Company
>>
>> --
>> Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgadmin-hackers
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
