karave...@mail.bg writes: > ----- Цитат от Alex Shulgin (a...@commandprompt.com), на 14.05.2012 в 18:16 > ----- > >> Alex <a...@commandprompt.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
We call it that way since we rely on existing libpq code to interpret the value of every parameter in the URI (well, almost: with notable exception of translating "ssl=true" for JDBC compatibility.) I don't think anyone would confuse host part of the URI with URI parameter "?host=..." if we care to express things clearly in the documentation (which we do I believe.) Existing implementations, like that mentioned by Peter in the top message of this thread (SQLAlchemy or was it psycopg2?) already use this notation, so I don't think we can or should do anything about this, i.e. there's little point in renaming to "path" or merely supporting it as an alternative syntax. -- Alex -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
