| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: incompatible changes of PQsetdbLogin() |
| Date: | 2000-10-17 15:26:43 |
| Message-ID: | Pine.LNX.4.21.0010171724000.980-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii writes:
> It seems some incompatible changes have been made between 7.0 and
> current. In 7.0, if a parameter is NULL OR a null string (""), then
> the value from an environment variable is applied. However in current
> ONLY NULL is considered. Is there any reason for this?
Yes, there are several reasons. First, to be consistent with
PQconnectdb(). Second, to be able to override a set environment variable
with an empty value. Third, because the existing behaviour was deemed to
be quite useless. See Oct 2 thread "libpq PGHOST". Is there a problem?
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-17 15:28:46 | Re: PL/Perl compilation error |
| Previous Message | Alex Pilosov | 2000-10-17 15:11:32 | Re: PL/Perl compilation error |