On Mon, 2006-09-25 at 08:25 -0300, Stephen Chisholm wrote:
> On Sat, Sep 23, 2006 at 11:08:05AM -0400, Rick Morrison wrote:
>
> > I think that psycopg2 will automatically use a Unix socket if a host address
> > is omitted on the connection call. You'd need a way to have SA not supply
> > that -- n
On Sep 25, 2006, at 7:25 AM, Stephen Chisholm wrote:
> Here is a method that works:
>
> If one runs a postgres server listening _only_ a Unix socket this code
> below shows how to connect and SA engine to it.
>
>import sqlalchemy as sa
>
>conn_args = {
>'host':'/tmp/pg',
>
On Sat, Sep 23, 2006 at 11:08:05AM -0400, Rick Morrison wrote:
> I think that psycopg2 will automatically use a Unix socket if a host address
> is omitted on the connection call. You'd need a way to have SA not supply
> that -- not sure how that would fit in with the dburi way of things. What's
>
on my machine, I am able to connect if I simply say:
create_engine('postgres://user:pass@/dbname')
i would assume that its dropping into a unix socket. im not an
expert at reading the unix sockets listing on OSX's netstat but I
also see an additional "PGSQL.5432" entry pop up when I
On Sat, Sep 23, 2006 at 11:08:05AM -0400, Rick Morrison wrote:
> I think that psycopg2 will automatically use a Unix socket if a host address
> is omitted on the connection call. You'd need a way to have SA not supply
> that -- not sure how that would fit in with the dburi way of things. What's
>
I think that psycopg2 will automatically use a Unix socket if a host address is omitted on the connection call. You'd need a way to have SA not supply that -- not sure how that would fit in with the dburi way of things. What's the big deal with using localhost anyway? I was under the impression tha
6 matches
Mail list logo
