From: | Florian Weimer <fweimer(at)bfk(dot)de> |
---|---|
To: | Alex Shulgin <ash(at)commandprompt(dot)com> |
Cc: | Greg Smith <greg(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: URI connection string support for libpq |
Date: | 2012-02-24 13:07:21 |
Message-ID: | 82k43cz8fq.fsf@mid.bfk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Alex Shulgin:
> Yeah, this is really appealing, however how do you tell if the part
> after the last slash is a socket directory name or a dbname? E.g:
>
> psql postgres:///path/to/different/socket/dir (default dbname)
> psql postgres:///path/to/different/socket/dir/other (dbname=other ?)
The HTTP precent is to probe the file system until you find something.
Most HTTP servers have something similar to the PATH_INFO variable which
captures trailing path segments.
It's ugly, but it's standard practice, and seems better than a separate
-d parameter (which sort of defeats the purpose of URIs).
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Shulgin | 2012-02-24 13:16:53 | Re: WIP: URI connection string support for libpq |
Previous Message | Alex Shulgin | 2012-02-24 13:01:12 | Re: WIP: URI connection string support for libpq |