| From: | karavelov(at)mail(dot)bg |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: libpq URL syntax vs SQLAlchemy |
| Date: | 2012-05-14 17:29:38 |
| Message-ID: | ca7361604ceef491a248d950d676695d.mailbg@mail.bg |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
----- Цитат от Alex Shulgin (ash(at)commandprompt(dot)com), на 14.05.2012 в 18:16 -----
> Alex <ash(at)commandprompt(dot)com> writes:
>
>
> The host part in this case is empty (it is "hidden" between the "//" and
> the following "/",) thus local socket connection is employed for this
> type of URIs. To specify non-standard path to the local sockets
> directory use the familiar URI parameter:
>
> postgres:///db?host=/path/to/socket/dir
>
And why are we calling "host" the parameter that specifies the path for socket
dir - it is not host and could be confused with the host part of the URI (the
part between // and /). Why do not call it "path" ? So it will become:
postgres:///db?path=/path/to/socket/dir
Best regards
--
Luben Karavelov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex | 2012-05-14 17:55:24 | Re: libpq URL syntax vs SQLAlchemy |
| Previous Message | Jeff Janes | 2012-05-14 16:56:13 | Re: Draft release notes complete |