From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #204: Confirm the environment variable of plugin |
Date: | 2010-06-09 06:41:05 |
Message-ID: | 054.5bffec92a09f7c6f02601fc72f18bdd8@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#204: Confirm the environment variable of plugin
---------------------------+------------------------------------------------
Reporter: Hiroshi Saito | Owner: Hiroshi Saito
Type: bug | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: 1.10
Keywords: core | Platform: all
---------------------------+------------------------------------------------
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?
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/204>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2010-06-09 06:41:31 | Re: [pgAdmin III] #204: Confirm the environment variable of plugin |
Previous Message | pgAdmin Trac | 2010-06-09 06:39:28 | Re: [pgAdmin III] #203: If plpgsql does have out parameter, it fails to debug. |