Re: libpq URL syntax vs SQLAlchemy - Mailing list pgsql-hackers

From karavelov@mail.bg
Subject Re: libpq URL syntax vs SQLAlchemy
Date
Msg-id ca7361604ceef491a248d950d676695d.mailbg@mail.bg
Whole thread Raw
In response to libpq URL syntax vs SQLAlchemy  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: libpq URL syntax vs SQLAlchemy
List pgsql-hackers
----- Цитат от Alex Shulgin (ash@commandprompt.com), на 14.05.2012 в 18:16 ----- <br /><br />> Alex  writes: <br
/>><br />> <br />> The host part in this case is empty (it is "hidden" between the "//" and <br />> the
following"/",) thus local socket connection is employed for this <br />> type of URIs. To specify non-standard path
tothe local sockets <br />> directory use the familiar URI parameter: <br />> <br />>
postgres:///db?host=/path/to/socket/dir<br />> <br /><br />And why are we calling "host" the parameter that
specifiesthe path for socket <br />dir - it is not host and could be confused with the host part of the URI (the <br
/>partbetween // and /). Why do not call it "path" ? So it will become: <br /><br
/>postgres:///db?path=/path/to/socket/dir<br /><br />Best regards <br /><br />-- <br />Luben Karavelov 

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Draft release notes complete
Next
From: Alex
Date:
Subject: Re: libpq URL syntax vs SQLAlchemy